Emanuel Gómez

🚀 Exploring the Top 10 Most Popular C#/.NET Libraries in 2025! As a .NET developer, leveraging the right libraries can boost productivity, improve code quality, and accelerate development. Here’s my list of the 10 libraries I see most commonly used in professional C#/.NET projects: 1️⃣ Newtonsoft.Json (Json.NET) – Advanced JSON serialization & deserialization. 2️⃣ Entity Framework Core – Powerful ORM for relational databases. 3️⃣ Serilog – Structured logging made easy. 4️⃣ xUnit / NUnit / MSTest – Unit testing frameworks for reliable code. 5️⃣ Dapper – High-performance micro-ORM for direct SQL queries. 6️⃣ Polly – Resilience and fault-handling library (retry, circuit breaker, fallback). 7️⃣ FluentValidation – Fluent object validation, keeping your models clean. 8️⃣ MediatR – Mediator pattern implementation for decoupling commands & queries. 9️⃣ Swashbuckle / NSwag – Automatically generate Swagger/OpenAPI documentation. 🔟 System.Text.Json – Fast native JSON handling built into .NET. 💡 Bonus mentions: Hangfire, Refit, MassTransit, RabbitMQ.Client – useful for background jobs, API clients, and messaging. Using these libraries wisely can simplify your code, increase maintainability, and save countless hours in development. Which of these do you use the most in your projects? Or do you have other favorites? Let’s discuss! 👇 #dotnet #csharp #programming #developers #softwareengineering

14

1 Comment

Can we stop putting “SOLID” in .NET job requirements in 2025? It’s 2025 and we’re still treating SOLID like it’s a litmus test for seniority. Modern .NET engineers are shipping functional cores, vertical slices, explicit delegates, composable pipelines, and event driven systems. Nobody is sitting around debating Liskov substitutions while designing real workloads. If you want strong engineers, ask for skills that matter today: reasoning about boundaries, modeling with clarity, designing for reliability and change, and not turning every solution into a dependency circus. SOLID isn’t harmful, it’s just outdated as a hiring filter. We moved on. Job descriptions should too.

785

181 Comments

🚀 From .NET to React/Next: Delivering a Real Industrial System in Production After years working with .NET and Angular, I took on a new challenge: building and delivering a web system from scratch for an industrial client who needed mobility, their own user management, and integration with the ERP. I’m proud to share that the project is now fully delivered and operating live at the client’s factory! 🛠️ The Challenge: Create a lightweight web app with a custom user management module, fast enough to run on data collectors across the factory floor. Operators use these devices to record production movements directly into the ERP via API — everything fully integrated and seamless. ⚙️ Tech Stack: • React for dynamic UI and state management • Next.js for routing, SSR, and a solid project structure • Prisma as the ORM for efficient, modern database operations • Tailwind CSS for a rapid, responsive and user-friendly interface • NextAuth.js for secure authentication and protected routes ✅ Key Deliveries: • User management: Full module for user registration, editing, blocking/unblocking, deleting, and permission control. • Security: NextAuth.js for secure login and route protection, ensuring that only authorized users access sensitive features. • Integration with ERP: Operators register production movements in real time, straight from the shop floor to the ERP. • UX for industry: Responsive screens and flows optimized for fast actions on mobile devices and data collectors. • Production-ready architecture: Clean code, robust integrations, and maintainability for future updates. 🔍 Takeaway: Delivering this industrial system using React, Next.js, Prisma, Tailwind, and NextAuth.js has been a major upgrade in my journey as a developer — proving that, no matter how experienced you are, there’s always room to learn, adapt, and deliver impact. If you’re working with new stacks, delivering for industry, or want to talk about integration and real-world challenges, let’s connect! Follow me here on LinkedIn for more stories and tech insights! #React #Nextjs #Prisma #Tailwind #NextAuth #ERP #SoftwareDevelopment #Industry #Security #Delivery #CareerGrowth

31

2 Comments

Pattern matching is handy in C#. The Type pattern tests the variable to see if it matches a given type. The Declaration pattern checks if the variable matches the type and assigns the result to a declared variable. Do you use these patterns?

107

8 Comments

Scoped vs. Singleton vs. Transient in .NET - How They Differ? Ever wondered which service lifetime to choose when registering dependencies in .NET? Here’s a breakdown of each: Transient - Creates a new instance every time it’s requested. - Lightweight and stateless by nature. - Ideal for short-lived operations or isolated tasks. Scoped - Creates one instance per HTTP request. - Shares the same instance across the request pipeline. - Useful for UoW patterns and request-specific data. Singleton - Creates one instance for the entire app lifetime. - Reused across all requests and threads. - Best for caching, configuration or shared services. When to Use? Transient → For stateless, short-lived tasks. Scoped → For services tied to a single request. Singleton → For shared data and long-living services. 👉 Want to dive deeper into each? Swipe! ——— 🔔 Follow Asim Noor for more .NET insights! ♻️ Repost to help your network!

293

18 Comments

Stop Looping when LINQ can do it faster (and cleaner)! 📌 More readable 📌 Often more performant 📌 Less room for bugs LINQ isn't just shorter—it's expressive and functional. What’s your favorite LINQ trick? #csharp #dotnet #linq #performance #cleancode #fullstackdeveloper

64

1 Comment