Katsiaryna Lunchuk

Does my application need Vitamin C? Introduce Health Checks to see if it is healthy ⬇️ Health Checks in ASP(.)NET are a way to assess the health of an application and its dependencies. They are used to monitor the status and performance of various components of an application, such as databases, external services, or internal services. Health Checks provide insights into whether an application is running as expected or if there are issues that need to be addressed. In the following article, I explained: - How to add Health Checks to your app - How to create Custom Health Checks - The way you can use built-in health checks - How to enable UI - Writing custom output Read it here: https://lnkd.in/dVYsrDe6 __ P.S. It was TheCodeMan Newsletter issue. Don't miss the next one, more than 17,000 subscribers will read it: thecodeman.net

199

7 commentaren

🚀 𝐈𝐎𝐩𝐭𝐢𝐨𝐧𝐬 𝐯𝐬 𝐈𝐎𝐩𝐭𝐢𝐨𝐧𝐬𝐒𝐧𝐚𝐩𝐬𝐡𝐨𝐭 𝐯𝐬 𝐈𝐎𝐩𝐭𝐢𝐨𝐧𝐬𝐌𝐨𝐧𝐢𝐭𝐨𝐫 𝐢𝐧 .𝐍𝐄𝐓 — 𝐖𝐡𝐚𝐭’𝐬 𝐭𝐡𝐞 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐜𝐞? ⁉️ 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐭𝐡𝐞 𝐎𝐩𝐭𝐢𝐨𝐧𝐬 𝐩𝐚𝐭𝐭𝐞𝐫𝐧? You can represent related settings using classes, which gives you strong typing for those settings. By applying this pattern, your app follows two important software engineering principles: 🔒 𝐄𝐧𝐜𝐚𝐩𝐬𝐮𝐥𝐚𝐭𝐢𝐨𝐧 – services only depend on the settings they actually use. 🧩 𝐒𝐞𝐩𝐚𝐫𝐚𝐭𝐢𝐨𝐧 𝐨𝐟 𝐜𝐨𝐧𝐜𝐞𝐫𝐧𝐬 – configuration logic is separated from business logic.  𝐈𝐎𝐩𝐭𝐢𝐨𝐧𝐬 • Reads configuration once at startup. • ❌ Doesn’t update if config changes while the app is running. • 🟢 Registered as Singleton, can be injected anywhere.  𝐈𝐎𝐩𝐭𝐢𝐨𝐧𝐬𝐒𝐧𝐚𝐩𝐬𝐡𝐨𝐭 • Reads configuration fresh on every request. • Useful for per-request updates (e.g., in web apps). • 🟡 Registered as Scoped, so cannot be injected into Singletons.   𝐈𝐎𝐩𝐭𝐢𝐨𝐧𝐬𝐌𝐨𝐧𝐢𝐭𝐨𝐫 • Supports real-time updates without restarting the app. • Can trigger callbacks when config changes. • 🟢 Registered as Singleton, safe to inject anywhere. 💡 Quick Summary • IOptions → Static, simple, app startup only. • IOptionsSnapshot → Per-request updates. • IOptionsMonitor → Real-time updates with change notifications. ❓ Which one have you used the most in your projects? #DotNet #DotNetCore #AspNetCore #DotNetDeveloper #CSharp #DotNetTips

191

31 commentaren

💡 My Interview Experience in .NET Core & React – What Really Matters 💡 Recently, I’ve been through multiple .NET Core + React interviews, and I realized one thing: 👉 It’s not just about knowing the concepts, it’s about how you explain and apply them. interviewer mostly looking for real time knowledge. 🔹 Topics that were most important across interviews: .NET Core – Dependency Injection, Middleware, Caching, Repository Pattern, API Security, CI/CD with Azure DevOps React – State Management (Redux/Thunk/Saga), Hooks (useEffect, useMemo, useCallback), Component Communication, Performance Optimization Architecture – Explaining layers (Controller, Business, Data Access, Utilities, Models), Clean Architecture, and Deployment Strategy (Blue-Green, Canary, Azure DevOps Pipelines) 🔹 What interviewers expect: Don’t just define a topic → connect it to a real-time project use case. Show clarity → explain the flow (e.g., how a request passes through Middleware or how Redux manages async calls). In architecture discussions → always highlight scalability, security, and maintainability. Use this simple framework: Concept → Real-time Use Case → Example → Why it matters. ✨ Many developers prepare hard but miss the way of structuring answers – and that’s where they lose impact. That’s why I’ve started sharing my learnings here and also doing one-to-one guidance with anyone who needs it. If you’re preparing for .NET Core + React interviews and struggling with how deep to go or what to highlight in architecture questions, feel free to connect or drop me a message. Let’s learn, share, and grow together 🚀 #DotNetCore #ReactJS #FullStackDevelopment #InterviewPreparation #CareerGoal

169

8 commentaren

Finally new Angular Space article!!! Eduard Krivánek has been diving into some #Angular features that don’t get nearly as much attention as signals or computed ⚪️ effect 🔵 afterRenderEffect, ⚫️ afterNextRender, 🔴 afterEveryRender, and Renderer2. I kept mixing them up myself, so I’m glad Eduard Krivánek decided to untangle when to use which, how they differ, and how they behave with SSR. Article: https://lnkd.in/dnKXWpQy

72

5 commentaren

Can you implement Clean Architecture without the layers? Yes. Here's how. The main idea behind Clean Architecture is managing the direction of dependencies. All dependencies should point to the center - the application core. In .NET, it's common to achieve this by separating code into projects. Why? Separate projects make it easier to control dependencies. But it's really just folders on the file system and compiler rules. What's stopping you from having one project with all the "layers"? Nothing. Except... Now it becomes easy to "break" the rules of Clean Architecture. If your team is disciplined and knows what they're doing, no problem. But most teams need the safeguard that project separation provides. I talked about architecture tests in the past. Here's a quick guide to architecture testing: https://lnkd.in/eRcuWp5s Architecture tests can help you enforce the direction of dependencies. What do you think about this idea? --- Sign up for the .NET Weekly with 72K+ other engineers, and get a free Clean Architecture template: https://lnkd.in/ekMyTe3N

478

39 commentaren

upgrading from Angular 19 to 20 has surprisingly many renamings if you are maintaining a large project, these renamings mean extra care during upgrade, to ensure everything works as expected after breaking changes use the Angular Upgrade guide: https://lnkd.in/e_FTVpax

63

7 commentaren

🔥 Angular 21: FormArrayDirective 👀 Previously, you could only use FormArray within a parent FormGroup using formArrayName. There was no way to use a standalone FormArray directly in templates. Now you can use, [formArray] directive that works similarly to [formGroup] but for arrays. Note: this new directive will conflict with existing custom FormArray directives or formArray inputs on the same element. Migration may be required for applications using custom implementations. Thank you Matthieu Riegler https://lnkd.in/dVAdQ2D3

161

3 commentaren

Are you a .NET developer? Are you following proper coding standards and writing clean, scalable code? In our projects, we use .editorconfig to enforce consistency and best practices. From naming conventions (like async methods ending with Async, private fields prefixed with _) to code style rules, this helps us keep our codebase clean, maintainable, and team-friendly. If you are a fresher or preparing for interviews, this is a pro tip: Understanding these rules will show you how things work in real-time projects. I’ll be sharing more such tips regularly. Follow Sai Reddy for practical .NET, SQL, and full-stack development insights. Reach out to me to attend mock interviews that will help you prepare and confidently ace your next interview.  https://lnkd.in/gsrnePyD or https://lnkd.in/gmQQGgns  or https://lnkd.in/g3xnx-vh or https://lnkd.in/gswwEDZh or https://lnkd.in/gy6SDTDS or https://lnkd.in/gUjdagq7 or https://lnkd.in/gagfpvDj OR https://lnkd.in/gjm7naaH https://lnkd.in/gbR-MrVy #editorcofig #dotnetdevloper #c# #dotnet #Saireddy #saireddy-dotnetfs #dotnetfs

23