C# & .NET Daily’s Post

🎯 User-Defined Functions & User-Defined Types in Power Apps 💡 The foundation for modular, maintainable, and scalable low-code development. If you’re building Power Apps at scale — across multiple screens, teams, or even apps — UDFs (User-Defined Functions) and UDTs (User-Defined Types) are your new best friends. 🧠⚡ Here’s the quick overview 👇 🔹 User-Defined Functions (UDFs) Define once, reuse everywhere. ➡️ Create custom Power Fx functions to centralize logic. ➡️ Keep formulas clean, consistent, and fast. ➡️ Perfect for formatting, validation, visibility, or scoring rules. 🧩 Example: SetGreeting(name: Text) As Text = "Hello, " & name & "!" Set(Label1.Text, SetGreeting("Paul")) 🔹 User-Defined Types (UDTs) Define data structures once, use them across apps. ➡️ Think of them like "mini-models" for your app data. ➡️ Strong typing for predictable logic. ➡️ Reusable models like Project, Employee, or Task. 🧱 Example: Type Project = { Name: Text, StartDate: Date, Owner: Text }; Set(MyProject, { Name: "Copilot Rollout", StartDate: Today(), Owner: "Marcel" }); 🚀 Together, UDFs + UDTs enable: ✅ Modular app architecture ✅ Easier maintenance ✅ Cleaner logic ✅ Scalable reuse 🧠 Pro Tip: Use App → Functions for UDFs and Power Fx Type syntax for UDTs. Combine them for reusable, enterprise-grade logic across your environment. 💬 What’s your favorite use case for UDFs or UDTs so far? #PowerApps #PowerFx #LowCode #M365 #PowerPlatform #AppDevelopment #Makers #CopilotStudio

MVVM Architecture – Why It Matters in Modern App Development When building apps, managing UI updates and business logic can get messy fast. That’s where MVVM (Model–View–ViewModel) steps in. What it solves: - Keeps UI code clean and focused - Reduces duplicate logic across screens - Makes apps easier to maintain and scale - Works beautifully with reactive data flows (LiveData / StateFlow) How it’s structured: Model: Data source layer (API, DB, Repository) View: UI layer (Activity/Fragment/Compose UI) ViewModel: Middle layer that holds state & business logic The View observes the ViewModel. No direct calls → no tight coupling → fewer bugs. Example flow: User clicks a button → ViewModel updates state → UI auto-refreshes.

🚀 From embedded systems to desktop apps: we're excited to share that for the next few weeks we will be focused on improving features in Slint to make it production-ready for desktop application development. We are working together with Urban B., maintainer of the #LibrePCB project, supporting the transition of their #Qt-based GUI to a #Slint-based GUI. Learn more about the features that are being implemented in our blog https://lnkd.in/e9yKe3DW #UI #CrossPlatform #OpenSource #DesktopApps

🗂️ Model-Driven Apps: The Architecture Checklist That Prevents Failure Model-Driven apps fail when you skip the fundamentals. After building 50+ enterprise apps, these are non-negotiable: 📊 Data First: Model your data before touching the UI Use standard Dataverse tables when possible Set cascade rules correctly (or lose data) Index filtered columns 🔐 Security That Scales: Start with least privilege Clone existing roles, don't build from scratch Remember: Users need Read access just to see your app Append/Append To privileges for lookups ⚡ Performance Markers: Views: Limit columns to essentials Forms: Use tabs to defer loading Plugins: Async where possible (2-minute timeout) Business rules: 10 per entity maximum The difference between good and great Model-Driven apps? Planning your data model properly. Everything else follows. #ModelDrivenApps #Dataverse #PowerPlatform #EnterpriseApps #BusinessApplications #Finance #HR #Engineering #Energy #Power

🗂️ Model-Driven Apps: The Architecture Checklist That Prevents Failure Model-Driven apps fail when you skip the fundamentals. After building 50+ enterprise apps, these are non-negotiable: 📊 Data First: Model your data before touching the UI Use standard Dataverse tables when possible Set cascade rules correctly (or lose data) Index filtered columns 🔐 Security That Scales: Start with least privilege Clone existing roles, don't build from scratch Remember: Users need Read access just to see your app Append/Append To privileges for lookups ⚡ Performance Markers: Views: Limit columns to essentials Forms: Use tabs to defer loading Plugins: Async where possible (2-minute timeout) Business rules: 10 per entity maximum The difference between good and great Model-Driven apps? Planning your data model properly. Everything else follows. #ModelDrivenApps #Dataverse #PowerPlatform #EnterpriseApps #BusinessApplications #Finance #HR #Energy

When should you use CQRS in your .NET app? ✅ Complex domains ✅ High read/write scaling needs ✅ Separate models make sense ❌ Don’t overdo it for simple CRUD Use CQRS for clarity and performance — not for everything. #dotnet #cqrs #architecture #csharp #cleanarchitecture

💡Laravel Tip: Let Your Models Think for Themselves Stop formatting data manually in your controllers or services. Let your Eloquent models handle that automatically using Mutators, Accessors, and Casts. ✅Input sanitization happens automatically ✅JSON data becomes structured instantly ✅No more repetitive formatting logic When models are smart, your controllers stay clean and your app becomes maintainable at scale.

NET 10 Cheat Sheet: Key Features & Updates .NET 10 brings significant improvements to boost app performance, cloud-native capabilities, AI integration, and developer experience targeting modern workloads on multiple platforms.

𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐀𝐒𝐏.𝐍𝐄𝐓 𝐂𝐨𝐫𝐞: 𝐖𝐞𝐛𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐁𝐮𝐢𝐥𝐝𝐞𝐫 𝐯𝐬 𝐖𝐞𝐛𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 ✅𝐖𝐞𝐛𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐁𝐮𝐢𝐥𝐝𝐞𝐫 - It is used to 𝐜𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐞 𝐚𝐧𝐝 𝐛𝐮𝐢𝐥𝐝 your web application 𝐛𝐞𝐟𝐨𝐫𝐞 𝐢𝐭 𝐫𝐮𝐧𝐬.     - You use it to:       - Set up 𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬 (like 𝐀𝐝𝐝𝐂𝐨𝐧𝐭𝐫𝐨𝐥𝐥𝐞𝐫𝐬(), 𝐀𝐝𝐝𝐃𝐛𝐂𝐨𝐧𝐭𝐞𝐱𝐭())         - 𝐂𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐞 𝐬𝐞𝐭𝐭𝐢𝐧𝐠𝐬 (like appsettings.json)         - S𝐞𝐭 𝐮𝐩 𝐥𝐨𝐠𝐠𝐢𝐧𝐠, 𝐜𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐚𝐭𝐢𝐨𝐧, 𝐝𝐞𝐩𝐞𝐧𝐝𝐞𝐧𝐜𝐲 𝐢𝐧𝐣𝐞𝐜𝐭𝐢𝐨𝐧.    🔧 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: var builder = WebApplication.CreateBuilder(args); builder.Services.AddControllers(); builder.Services.AddDbContext<MyDbContext>(); ✅ 𝐖𝐞𝐛𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 - This is the 𝐚𝐜𝐭𝐮𝐚𝐥 𝐚𝐩𝐩 you run after configuration.     - You use it to:       - Build the 𝐦𝐢𝐝𝐝𝐥𝐞𝐰𝐚𝐫𝐞 𝐩𝐢𝐩𝐞𝐥𝐢𝐧𝐞         - 𝐌𝐚𝐩 𝐫𝐨𝐮𝐭𝐞𝐬 and endpoints like MapControllers()         - 𝐒𝐭𝐚𝐫𝐭 𝐭𝐡𝐞 𝐚𝐩𝐩 using Run()       🔧 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: var app = builder.Build(); app.UseHttpsRedirection(); app.UseAuthorization(); app.MapControllers(); app.Run(); WebApplicationBuilder = setup and configuration. WebApplication = actual running and execution. 𝐘𝐨𝐮 𝐜𝐚𝐧 𝐬𝐚𝐲: 𝐓𝐡𝐞 "𝐁𝐮𝐢𝐥𝐝𝐞𝐫" 𝐛𝐮𝐢𝐥𝐝𝐬, 𝐚𝐧𝐝 𝐭𝐡𝐞 "𝐀𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧" 𝐫𝐮𝐧𝐬. #ASPNetCore #DotNet #BackendDevelopment

3 Insights from my Desktop App Instead of buying ready-made software, I decided to build my own application — mainly because I wanted full control of my data and to keep it securely on my own system. Data Backup Matters Most — 3-2-1 backup rule: 3 copies of data, on 2 different mediums, with 1 kept offsite. When my application first crashed it wiped everything it was disaster to recover that , so precautions is better than prevention. Choose the Right Tech Stack — pick a technology with a rich modern UI and strong long-term support. Apart from app itself I had to built custom components that took lots of time, even licencing and updater I built myself cause there was no feasible over the self solution Build for the Right Device — Initially, I focused on desktop since a keyboard speeds up billing. But observing others, I realized a tablet version could have been more flexible for shop use. Building it myself was challenging but deeply rewarding — it taught me not just coding, but how to think like a product owner. Bonus tip u will find 50% of code on GitHub , choose stack overflow over AI , learn from books #SoftwareDevelopment #LearningByBuilding #JavaFX #SmallBusiness #GoldShop