Stefan Đokić

#dotNET is back! Plain Concepts is cooking something again. Another dotNET edition for this year with more than 20 speakers 🚀🚀 Who is coming?? ➡️ Get more info and details about talks and speakers here: https://lnkd.in/dbFMxvsh #dotnet2024 #IA #ML #development #cloud #Azure #data #MS

34

4 Comments

Right from the oven, the latest book of Dino Esposito. Of course I couldn’t miss it. Is not only about the information, but the style how Dino is explaining concepts. #cleanarchitecture #dotnet

35

2 Comments

Avoid IHostedService before .NET 8 if you can, because it has a problem... 👇 In .NET versions before 8, the 𝐒𝐭𝐚𝐫𝐭𝐀𝐬𝐲𝐧𝐜 methods of 𝐈𝐇𝐨𝐬𝐭𝐞𝐝𝐒𝐞𝐫𝐯𝐢𝐜𝐞 implementations were called one after the other during application startup. Each StartAsync method had to be finished before the next one could begin, which could delay the startup if any service took a long time to initialize. Imagine you have a task that executes for a couple of minutes. This means the application would not start until that task is finished. .NET 8 introduces a solution with the 𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬𝐒𝐭𝐚𝐫𝐭𝐂𝐨𝐧𝐜𝐮𝐫𝐫𝐞𝐧𝐭𝐥𝐲 property in the HostOptions class. With services now starting concurrently, the host’s startup time is minimized to the duration of the slowest service's StartAsync method, rather than being the combined time of all services. Note: Each service begins only after the previous one releases control by reaching its first await statement in the StartAsync method. To allow the next service to start as quickly as possible, ensure that StartAsync is truly asynchronous and avoid any costly operations before the first await. Like the post? You'll enjoy with 13k+ engineers in this free community TheCodeMan.net.

262

15 Comments

🚀 **Enhance Your .NET Skills and Elevate Your Career** 🚀 As technology rapidly evolves, the role of a .NET developer has never been more critical! Whether you're just starting or have been in the field for years, here are a few key areas every .NET developer should focus on to stay ahead: ### 1. **Master ASP.NET MVC** ASP.NET MVC remains at the core of web application development, offering a flexible framework for building dynamic, robust applications. Mastering this will allow you to deliver high-performing web applications that are scalable and easy to maintain. ### 2. **Deep Dive into C#** As the foundation of .NET development, staying up-to-date with the latest C# versions is a must. Focus on understanding the language's new features, patterns, and best practices to write clean, maintainable code. ### 3. **SQL Server & Database Management** No application is complete without data! A solid understanding of SQL Server, stored procedures, and efficient query optimization is key to developing performant applications. ### 4. **Build APIs with .NET Core** With microservices and distributed systems on the rise, learning how to build efficient APIs using .NET Core is a vital skill. .NET Core allows you to create lightweight, cross-platform applications, which is essential in today's diverse tech ecosystem. ### 5. **Cloud Integration with Azure** As businesses shift to cloud solutions, integrating your .NET applications with cloud platforms like Azure can give you a significant edge. Explore how services like Azure Functions, App Services, and Azure DevOps can streamline your development process and enhance application scalability. ### 6. **Embrace Front-End Technologies** Though .NET is back-end-centric, full-stack development is becoming the standard. Familiarize yourself with front-end technologies such as Angular, React, and JavaScript to complement your .NET skills and deliver seamless, end-to-end solutions. ### 7. **Test, Test, Test!** Automated testing frameworks like NUnit and xUnit should be in every developer's toolbox. Quality code isn't just about functionality—it's about reliability, scalability, and ease of maintenance. ### 8. **Stay Curious, Keep Learning** The .NET ecosystem is constantly evolving. Keep your skills sharp by learning about the latest advancements like Blazor, .NET 6/7, and MAUI for building cross-platform apps with .NET. As a .NET developer with a passion for continuous learning and innovation, I’m excited about the future of this dynamic field and eager to keep expanding my skills. Feel free to connect if you want to discuss all things .NET, SQL, cloud, or tech! #dotnetdeveloper #webdevelopment #Csharp #aspnetcore #SQLServer #Azure #APIs #SoftwareEngineering #TechLearning

5

I’d like to share my thoughts on Anthony G.’s book, *"Beginning gRPC with ASP.NET Core 6"*, a valuable guide for .NET developers venturing into the world of gRPC. Why is this book important? The book offers: - A comprehensive overview of gRPC and its advantages over REST APIs. - Practical examples for implementation in ASP.NET Core 6. - A full picture of using Protocol Buffers. - Best practices from architecture, security, and performance perspectives. Useful for scenarios like: - Building microservice architectures - Creating high-performance APIs - Establishing cross-platform communication between services - Migrating legacy WCF services to gRPC Strengths of the book: - Practical examples for real-world scenarios - Detailed explanations of concepts - Integration of modern technologies (Angular, TypeScript) - Full-stack coverage (from frontend to backend) Who would benefit: - .NET developers - Architects - Tech leads - DevOps engineers This book is an excellent resource for those who want to master gRPC within the .NET ecosystem and implement a modern microservices architecture. It can serve as a guide for planning and executing projects. #gRPC #dotNET #aspnetcore

40

Blogged: How to Write Contract Tests in C# With Pact - Provider Tests The third post in the contract testing series! Slowly but surely... #dotnet #testing #pact https://lnkd.in/gxP6EqvS

12

In addition to data in our program, we often need outside resources. Sometimes, these resources are provided by the end-user, but there are also situations where we have all the resources at the time of development. We need an option to ship them with our program somehow. Rather than merely attaching files to our program, it’s advantageous to include them within its assembly. This ensures they’re always readily available and eliminates the risk of overlooking them. The encapsulation of resources within the program itself constitutes embedded resources. In this article, we will talk more about embedded resources in #dotnet

23

Enea Jahollari presents a session titled “Migrating to Modern Angular” at #ngPolandConf. This talk focuses on practical steps and best practices for updating older Angular projects to the latest versions, covering key challenges and solutions encountered during the migration process. Enea will walk through important considerations such as handling deprecated dependencies, upgrading RxJS, implementing Angular’s latest features, and ensuring smooth transitions between Angular versions to maintain application stability and performance.

49

2 Comments

The #dotnet nuget cli might get a new command soon: "dotnet nuget why" And no - it will not tell you why it will not magically reduce the number of times you have to run nuget restore before your project actually builds. No - it will show you a complete graph of a given dependency and the transitive dependencies with their respective version! This can be beneficial as package dependency version resolution is a whole page with many edge cases (I will link it in the comments).

96

11 Comments

I had the pleasure of giving a talk about the current "Testing Situation" in #Angular at Angular Belgrade. I didn't just cover the available testing tools but also some guidelines on how to approach testing in general. Modern/Upcoming tools like Vitest or the Playwright Component Test Runner were also mentioned. Here are the slides https://lnkd.in/desDZG8c Хвала вам 🇷🇸

58

4 Comments

One of THE most underrated time savers in huge .NET projects: Having a solution where you can easily resolve merge conflicts. When several developers at once change the solution structure: - add a new project - reorganize projects into folders .sln files with all those GUIDs become a giant mess and cause merge conflict. Lately, Visual Studio introduced a new, simpler ".slnx" file format, That removes all those complicated GUIDs from the solution file. It's available starting from Visual Studio 2022 17.10 as a preview feature. To use it: In Tools -> Options -> Preview Features enable the "Use Solution File Persistence Model" Then File -> Save YourSolution.sln As... And pick .slnx file format. Going forward, it will improve readability. And help avoid painful merge conflicts. Bye, bye, confusing GUIDs, you won't be missed. *** P.S. Lack of simplicity, not lack of time, is a true enemy in every C# project. ❌ Big classes. ❌ Poorly written business logic. ❌ Over-engineered software architecture. Inside my newsletter, you get tools, strategies, and systems to eliminate code complexity. (based on my 12 years of experience) Come join 2,732 developers here: https://lnkd.in/djSGihGa

97

16 Comments

💡 When to prefer foreach over LINQ in C# and avoid the pitfalls of double execution? 💡 LINQ is often elegant and convenient, but did you know it can sometimes lead to double execution without the developer realizing it? In some cases, it’s wiser to use a simple foreach. 🚫 Why be cautious with LINQ? • Hidden double execution: LINQ uses lazy evaluation, which means that certain queries like Where() or Select() are only executed when they are actually iterated over. If a query is reused multiple times without being stored, it will be executed multiple times, potentially impacting performance. • When to favor foreach? : For complex processing or iterations over large collections, foreach often offers more control and better performance. Unlike LINQ, foreach guarantees there’s no hidden double iteration. ✅ Best practices: • Use ToList() or ToArray() to materialize your LINQ results and avoid multiple executions. • When readability or performance is key, foreach can be a better option, especially if you need to optimize every step of the iteration. LINQ is a great tool, but you need to be aware of its limits. For repeated or critical operations, foreach remains a simple and effective choice. #CSharp #DotNet #LINQ #Performance #Foreach #DevTips #Optimization

26

3 Comments

🔥✨Why ASP.NET Boilerplate is a Client's Best Friend Think of ASP.NET Boilerplate as the "Instant Pot" for software development. Why? It’s fast, consistent, and handles the complex "cooking" so we don’t have to. 🔹 Efficient: Reduces development time, so your project isn’t just another “someday” dream. 🔹 Secure: Built-in best practices mean better security without extra effort. 🔹 Customizable: It’s like getting a tailored suit… but in code. 🔹 Cost-Effective: Less time + fewer bugs = smaller bills for clients! ASP.NET Boilerplate keeps projects on track and clients happy. Who doesn’t love that? 😄 #SoftwareDevelopment #ASPNet #ClientSuccess

2

2 Comments

𝐁𝐚𝐥𝐚𝐧𝐜𝐢𝐧𝐠 𝐂𝐮𝐫𝐫𝐞𝐧𝐭 𝐖𝐨𝐫𝐤 𝐚𝐧𝐝 𝐅𝐮𝐭𝐮𝐫𝐞 𝐆𝐫𝐨𝐰𝐭𝐡: 𝐅𝐨𝐫 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐞𝐫𝐬 Many of us find ourselves focusing so intently on our current task, whether it's maintaining legacy systems like Wind forms in .NET Framework 3.5 or managing a growing backlog, that we neglect our skill development and preparation for future opportunities. While dedicating yourself to your present responsibilities is important, overemphasis on the now can hinder long-term growth. If we spend all our time solely on our current roles, we risk falling behind in the fast-evolving tech industry. It's essential to strike a balance between delivering on today's expectations and investing in tomorrow's skills. What's your thoughts on this drop them in comment section. Join WhatsApp Group of .NET Developers https://lnkd.in/dUXf4K_5 Like👍 & Repost ♻️

10

1 Comment

If you are starting a new project, you must first choose a tech stack. Project starter pack: - Backend: .NET - Mobile: .NET MAUI(or AvaloniaUI or Uno) - Frontend: Blazor or Angular - Database: SQL Server or PostgreSQL - Testing: xUnit + NSubstitute Depending on the project type, I mix and match various technologies. This list has evolved over time because the key is to have a tech stack that allows you to build a robust and maintainable product. Not just to follow trends. So, I’m curious… What is your preferred tech stack? ✍️ #Education #Schools #Tech #IT #Learn #ITSkills #Robotics #Softwaresolutions #Skilsforthefuture #Skills #Girlsintech #Enjoylearning #Backtoschool

4

The criticism that abstractions and design patterns receive in .NET is somewhat unjustified. When I build small applications, I approach them as if they might one day grow into large enterprise solutions. Yes, this approach involves more work, some of which may seem unnecessary at first. However, it has significantly deepened my understanding of software design and actually made it easier to simplify complex systems. For those eager to dive into abstractions and patterns, I suggest honing your skills by creating your own templates or adapting from others out there. This exercise can be invaluable in mastering the art of balancing complexity and simplicity in software design.

2

🎥 Why .NET for Cloud-Native Development? In the fast-paced IT industry, staying ahead with the right tools is a game-changer. .NET has become a top choice for #cloudnativedevelopment, offering a framework that makes your development smoother, faster, and more secure. In this video, Mario Alejandro Manzano we’ll explore the key features and advantages of using .NET for building high-performing, innovative applications as an overview of .NET 8 and .NET Aspire! 🔗 Watch now: https://lnkd.in/e67GpksA #CloudNative #NET #dotnet #dotnetdevelopment #dotnet8 #dotnetaspire

8

Nice explanation of the Unified Control State Change Events in Angular 18 https://lnkd.in/dZJcWDSX

3