Osama Khodroj’s Post

𝐑𝐮𝐧, 𝐔𝐬𝐞, 𝐚𝐧𝐝 𝐌𝐚𝐩 𝐌𝐞𝐭𝐡𝐨𝐝𝐬 𝐢𝐧 .𝐍𝐄𝐓 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 💡 In ASP.NET Core, the Run, Use, and Map extension methods are used to configure middleware in the application pipeline. Here's a breakdown of each method and its purpose: 1- 𝐑𝐮𝐧: The Run method is used to terminate the pipeline and generate a response. It should be used at the end of the middleware pipeline because it stops the pipeline from further processing. 2- 𝐔𝐬𝐞: The Use method is used to add middleware to the pipeline. It can handle requests and pass them to the next middleware in the pipeline using the next parameter. 3- 𝐌𝐚𝐩: The Map method is used to map middleware to specific request paths. It allows you to branch the middleware pipeline based on the request path.

𝐑𝐮𝐧, 𝐔𝐬𝐞, 𝐚𝐧𝐝 𝐌𝐚𝐩 𝐌𝐞𝐭𝐡𝐨𝐝𝐬 𝐢𝐧 .𝐍𝐄𝐓 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 💡 In ASP.NET Core, the Run, Use, and Map extension methods are used to configure middleware in the application pipeline. Here's a breakdown of each method and its purpose: 1- 𝐑𝐮𝐧: The Run method is used to terminate the pipeline and generate a response. It should be used at the end of the middleware pipeline because it stops the pipeline from further processing. 2- 𝐔𝐬𝐞: The Use method is used to add middleware to the pipeline. It can handle requests and pass them to the next middleware in the pipeline using the next parameter. 3- 𝐌𝐚𝐩: The Map method is used to map middleware to specific request paths. It allows you to branch the middleware pipeline based on the request path. 𝐈𝐟 𝐲𝐨𝐮 𝐟𝐢𝐧𝐝 𝐭𝐡𝐢𝐬 𝐮𝐬𝐞𝐟𝐮𝐥, 𝐫𝐞𝐩𝐨𝐬𝐭 ♻️ 𝐚𝐧𝐝 𝐬𝐩𝐫𝐞𝐚𝐝 𝐭𝐡𝐞 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞. 𝐅𝐨𝐥𝐥𝐨𝐰 🔔 Adnan Maqbool Khan 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭.

𝐑𝐮𝐧, 𝐔𝐬𝐞, 𝐚𝐧𝐝 𝐌𝐚𝐩 𝐌𝐞𝐭𝐡𝐨𝐝𝐬 𝐢𝐧 .𝐍𝐄𝐓 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 💡 In ASP.NET Core, the Run, Use, and Map extension methods are used to configure middleware in the application pipeline. Here's a breakdown of each method and its purpose: 1- 𝐑𝐮𝐧: The Run method is used to terminate the pipeline and generate a response. It should be used at the end of the middleware pipeline because it stops the pipeline from further processing. 2- 𝐔𝐬𝐞: The Use method is used to add middleware to the pipeline. It can handle requests and pass them to the next middleware in the pipeline using the next parameter. 3- 𝐌𝐚𝐩: The Map method is used to map middleware to specific request paths. It allows you to branch the middleware pipeline based on the request path. 𝐈𝐟 𝐲𝐨𝐮 𝐟𝐢𝐧𝐝 𝐭𝐡𝐢𝐬 𝐮𝐬𝐞𝐟𝐮𝐥, 𝐫𝐞𝐩𝐨𝐬𝐭 ♻️ 𝐚𝐧𝐝 𝐬𝐩𝐫𝐞𝐚𝐝 𝐭𝐡𝐞 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞. 𝐅𝐨𝐥𝐥𝐨𝐰 🔔 Adnan Maqbool Khan 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭.

𝐑𝐮𝐧, 𝐔𝐬𝐞, 𝐚𝐧𝐝 𝐌𝐚𝐩 𝐌𝐞𝐭𝐡𝐨𝐝𝐬 𝐢𝐧 .𝐍𝐄𝐓 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 💡 In ASP.NET Core, the Run, Use, and Map extension methods are used to configure middleware in the application pipeline. Here's a breakdown of each method and its purpose: 1- 𝐑𝐮𝐧: The Run method is used to terminate the pipeline and generate a response. It should be used at the end of the middleware pipeline because it stops the pipeline from further processing. 2- 𝐔𝐬𝐞: The Use method is used to add middleware to the pipeline. It can handle requests and pass them to the next middleware in the pipeline using the next parameter. 3- 𝐌𝐚𝐩: The Map method is used to map middleware to specific request paths. It allows you to branch the middleware pipeline based on the request path. 𝐈𝐟 𝐲𝐨𝐮 𝐟𝐢𝐧𝐝 𝐭𝐡𝐢𝐬 𝐮𝐬𝐞𝐟𝐮𝐥, 𝐫𝐞𝐩𝐨𝐬𝐭 ♻️ 𝐚𝐧𝐝 𝐬𝐩𝐫𝐞𝐚𝐝 𝐭𝐡𝐞 𝐤𝐧𝐨𝐰𝐥𝐞𝐝𝐠𝐞. 𝐅𝐨𝐥𝐥𝐨𝐰 🔔 Adnan Maqbool Khan 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭.

ASP.NET Core middleware is a piece of code integrated inside the application’s pipeline that we can use to handle requests and responses. When we talk about the ASP.NET Core middleware, we can think of it as a code section that executes with every request. Usually, we have more than a single middleware component in our application . Each component can:👇 • Pass the request to the next middleware component in the pipeline and also • It can execute some work before and after the next component in the pipeline. To build a pipeline, we are using request delegates, which handle each HTTP request. To configure request delegates, we use the 👉 Run, Map, and Use extension methods.

How to implement identity authentication in minimal APIs in ASP.NET Core https://lnkd.in/gfTxqiYr Minimal APIs in ASP.NET Core allow us to build lightweight APIs with minimal dependencies. However, often we will still need authentication and authorization in our minimal APIs. There are several ways to achieve this in ASP.NET Core including basic authentication, token-based authentication, and identity-based authentication. We discussed implementing basic authentication in minimal APIs here, and JWT token-based authentication in minimal APIs here. In this article we’ll examine how we can implement identity-based authentication for minimal APIs in ASP.NET Core. To read this article in full, please click here

Help me please with this problem: Service Reference was added. And after that C#-code with web serv Check it out: https://lnkd.in/di8JA686 Join the conversation! #c #webservices

ASP .NET Core provides an in-memory test server that we can use to spin up an application instance for running tests. You can use this to write awesome integration tests with Testcontainers. The custom IntegrationTestWebAppFactory will do a few things: - Create and configure a MsSqlContainer instance - Call ConfigureTestServices to set up EF Core with the container database - Start and stop the container instance with IAsyncLifetime Now, you can run your tests, and EF Core will use a real database under the hood. Learn more about this here: https://lnkd.in/eExW4V7P

EF Core Automatic Migrations in .NET Core Web API | .Net 8 Click here for source http://tiny.cc/xzekxz Do you want to know more click here http://tiny.cc/qc9cvz  Learn how to effortlessly implement EF Core Automatic Migrations in your .NET Core Web API projects. This tutorial provides a step-by-step guide to integrating automatic migrations into your development workflow, ensuring seamless database updates and management. #efcore #automaticmigrations #dotnetcorewebapi #dotnetcore #entityframework #databasemanagement #webdevelopment #backenddevelopment #tutorial

In ASP.NET Core, you might need to handle authorization within services instead of at the API level, especially for custom role or permission management. To explain this, let's consider a very simple use case: A logged-in user can create a new user across all tenants or only within a current tenant based on the permissions. Additionally, your software might auto-create users when an external identity provider verifies a JWT token and the linked user doesn't exist in your system. To implement this, we need a service that authorizes the current user or allows other internal services to create users without authorization. Here are some not recommended options: * Adding a property to the input model to disable the authorization * Creating separate classes for authorized and unauthorized operations * Using DbContext directly, bypassing domain logic I'll show you how to keep your code clean and maintainable, avoiding dirty input models and duplicated code. You just need to register IAuthorizationScope as a scoped service. This approach works well in unit testing.