Saad Abdelhaleem

✨ Tracking Change in Data in ASP.Net core web API and Log it in Database

٥٨

❓18 questions for Junior .NET developer interview (with answers)❓ Are you willing to join .NET developer Junior position? Or just want to start complicated training in .NET? Try to answer 10 most popular questions you may hear in the interview and check your answers in the first comment: 1. What is object-oriented programming? Describe its main principles. 2. What is the difference between managed and unmanaged code? 3. What is the difference between C and C#? 4. What is an object in the C# language? What is a program? 5. What is called a method in the C# language? 6. What is a structure in the C# language? 7. How does a garbage collector work in C#? What are the conditions for garbage collection? 8. What is an array? 9. What is recursion? 10. What are the types of design patterns? Can you provide examples of their usage? 11. What is REST API? Can you define it in your own words? 12. Can you provide an example of a SOLID principle violation? 13. Can you describe the best CI/CD pipeline you can imagine? 14. How would you address a growing technical debt? 15. What is multithreading and why do we need it? 16. When do you use asynchronous methods? 17. What is LINQ? 18. What are commonly used .NET collection types? Check the comments for answers. If you feel that you know more than half of these topics, try to apply to our part-time job with training opportunities in Turkiye by the link in the first comment.

٣٧

١ تعليق واحد

What is the purpose of middleware in ASP.NET Core? Middleware in ASP.NET Core is a software component responsible for processing requests and generating responses in the web application pipeline. It sits between the server side and the application and is designed to handle cross-cutting concerns, such as authentication, caching, logging, and routing. The primary purpose of middleware is to provide a modular way of processing HTTP requests and responses, allowing developers to add, remove, or reorder middleware components in the pipeline based on their specific needs. This makes it easy to customize the web application's behavior without modifying the core application logic. In addition, middleware can perform various tasks, such as modifying request or response headers, handling errors and exceptions, and executing asynchronous code. Middleware can also perform custom processing of requests and responses, such as generating dynamic content or formatting data. Overall, middleware plays a critical role in the architecture of ASP.NET Core applications, allowing developers to write modular, flexible, and extensible web applications that can be easily customized and scaled. #ASP.NET CORE #Middleware

٤

١ تعليق واحد

🔵 Boosting .NET Application Resilience with Polly 🔧 As software engineers, we often face challenges with transient faults and the reliability of external services. To tackle these issues effectively, leveraging the right tools is crucial. One such powerful tool in the .NET ecosystem is Polly – a comprehensive resilience and transient-fault-handling library. 🔵 Why Polly? Polly enables developers to define robust policies to handle transient faults like retries, circuit breakers, fallbacks, and more. This makes applications more resilient and ensures smoother operation, even in the face of unpredictable external factors. 🔵 Key Features of Polly: ✔️ Retry Policy: Automatically retries a failed operation a specified number of times with optional delay. ✔️ Circuit Breaker Policy: Breaks the circuit for a period after consecutive failures, preventing further calls until a timeout expires. ✔️ Fallback Policy: Provides a fallback action when an execution fails. Bulkhead Isolation: Limits the number of concurrent executions of a given policy, protecting system resources. ✔️ Timeout Policy: Specifies a timeout period for an operation, canceling it if it exceeds this time. ✔️ Cache Policy: Caches the results of operations to reduce the load on external resources. Installation: Install-Package Polly

١٢٦

٢٠ تعليق

Why Implement API Versioning? It allows you to support different versions of your API simultaneously. It enables you to safely introduce new features or changes without disrupting existing users. Here is an example of using API Versioning in ASP.NET Core Web API: 1- Install the NuGet Package: dotnet add package: Microsoft.AspNetCore.Mvc.Versioning 2- Configure API Versioning: In the ConfigureServices method, add the following services.AddApiVersioning(options => { options.ReportApiVersions = true; // Reports supported API versions in response headers options.AssumeDefaultVersionWhenUnspecified = true; // Uses the default version if not specified options.DefaultApiVersion = new ApiVersion(1, 0); // Sets the default API version }); 3- Create Versioned Controllers: Copy your existing controller and add the ApiVersion attribute. Also, update the Route attribute to reflect the version, as shown in the snapshots. 4- Test the API Versioning by calling the two different versions of your API: Version 1.0: GET /api/v1/products Version 2.0: GET /api/v2/products

٦

Asp .Net Crud Operation Using ajax

١٤

How to engineering distinguished software by 7 golden rules: 1-Apply best practices to ensure about deliveries' quality 2-Follow the Git Flow 3-Have strong principles of code review 4-Write tests as much as business gives you time 5-Be receptive to technical discussions 6-Automate as much as you can, ex: CI/CD 7-Write strong linter rules #software_engineer #flutter #mobile #kotlin #dart #java

٦

Best Practices for Improving Performance of ASP.NET Core Applications: Use caching: HTTP-based response caching Set by the Cache-Control header Distributed cache Use a distributed cache to store data that needs fast access. Caching with third-party libraries For example, Redis Cache In-memory caching In-memory caching uses the server's memory to store cached data. This type of caching is suitable for one or more servers.  Cache Tag Helper Use cache tag helper in MVC applications, for example: <cache expires-after="@TimeSpan.FromSeconds(120)"> Current Time Inside Cache Tag Helper: @DateTime.Now </cache> Always use asynchronous programming and avoid blocking requests: Recommendations: X  Do not use: Method calls that can block asynchronous calls by exiting Task.Wait orTask.Result. Avoid blocking at all stages of application development. ASP.NET Core is designed to run everything asynchronously. ✔  Use  Make 'hot code path' locations asynchronous. Make requests to the Data access layer and long API operations asynchronously. Make Controller methods asynchronous. The entire call stack is asynchronous, allowing you to take advantage of async/await patterns. Minimize large object allocations: Recommendations: X  Don't create  many large short-lived objects in the 'hot code path. ✔  Use  caching of large objects that are frequently used. Caching of large objects prevents expensive allocations. You can also use one of the classic  Flyweight patterns to work with such objects. ✔  Use ArrayPool<T>  for storing large arrays. Using a class ArrayPool<T> to "rent" and "return" buffers (using the Rent and Return methods) can improve performance in situations where arrays are frequently created and destroyed, resulting in significant memory pressure on the garbage collector. Optimizing Data Access Layer Efficient reading and writing of data is essential for good performance. Recommendations: ✔  Use  asynchronous requests to the Data access layer. ✔  Use  caching of frequently used data retrieved from a database or remote service (if business logic allows it). Depending on the scenario, use MemoryCache or DistributedCache. For more information, see Use Caching . ✔  Minimize  the number of requests to get data (the goal is to get data in one request, without making multiple requests) ✔  Use  LINQ query filtering and aggregation (for example, using .Where, .Select, or .Sum operators) to let the database do the filtering. X  Don't request  more data than necessary. Your requests should return only the data that is needed for the current HTTP request. X  Avoid  more than N + 1 problems

٣

Model binding in ASP.NET Core is a game-changer for efficiently handling incoming data in your web applications! Mastering attributes like [FromQuery], [FromRoute], and [FromBody] can significantly streamline our development process and reduce errors.

٤

٢ تعليق

ASP.Net Core Web API

٣

.Http file included with API project in .NET 8 👏 .http files as they allow us to send HTTP requests directly from within Visual Studio. From .NET 8 the API project template includes one by default which I think is great to expose more devs to them.

٣

Building scalable REST APIs from scratch using ASPNET CORE and C# By using the Entity framework to perform CRUD operations in SQL Server database Using Entity Framework Core in a code-oriented way Identifying and applying the repository pattern in ASPNET Core Web API Using Domain Driven Design (DDD) approach to create domain models and initial projects Familiarity with RESTful principles and their application in ASPNET Core Web API Add validation in ASPNET CORE Web API. Using popular third-party libraries such as AUTOMAPPER. Filtering, Sorting, Pagination in ASP.NET Core Web API. Image Upload In ASP.NET Core Web API. Securing our ASP.NET Core API - Authentication and Authorization - JWT Tokens Advanced Functionality in ASP.NET Core Web APIs as logging technique. Finally: Add Simple UI Project Using MVC pattern To Consume API. Link: https://lnkd.in/er6WSPkr

١٧

٤ تعليق

🔥new laravel package 🚀 Introducing the coding-partners/auto-controller Package! 🚀 My friend Yousef Saleh and I are thrilled to share a new Laravel package we've developed: coding-partners/auto-controller. This package allows you to quickly create fully functional controllers for any model in your project with just one command. It generates all the standard CRUD methods (create, read, update, delete), along with soft-delete methods, saving you a lot of time and effort. ✨ Key Features: - Full Controller Generation: Easily generate all CRUD operations and soft-delete methods for any model. - Comprehensive File Support: The package supports uploading all types of files—images, videos, audios, and documents—with high security. - Increased Productivity: Focus on building the core features of your project while the package handles the controller setup. 🔧 How to Use: Simply install the package via Composer and run a single command in the Artisan Console to generate the necessary controller. composer require coding-partners/auto-controller 💡 Example Usage: php artisan crud:generate Post ✨ After running the command, you'll have everything you need—FormRequests, API Resources, and optionally, a Service layer—all set up for you! 🔗 Open for Contributions: We welcome contributions! If you're interested in contributing to the development of this package, feel free to open an Issue or submit a Pull Request on GitHub. 📜 License: This package is licensed under the MIT License. --- We're excited to hear your thoughts! Check out the repository here: [GitHub Repo]( https://lnkd.in/eTX6NUyX ) #laravel #web_development #packages #backend #web #laravel_development #Auto_controller #coding_partners

٢٤

٨ تعليق

𝐑𝐮𝐧, 𝐔𝐬𝐞, 𝐚𝐧𝐝 𝐌𝐚𝐩 𝐌𝐞𝐭𝐡𝐨𝐝𝐬 𝐢𝐧 .𝐍𝐄𝐓 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 💡 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 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭.

١٧٩

٢٦ تعليق

𝐑𝐮𝐧, 𝐔𝐬𝐞, 𝐚𝐧𝐝 𝐌𝐚𝐩 𝐌𝐞𝐭𝐡𝐨𝐝𝐬 𝐢𝐧 .𝐍𝐄𝐓 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 💡 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 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭.

٣١٢

٣٩ تعليق

C# 7.2 introduced ref structs. But how are ref structs different from traditional structs? If you want to learn it, join more than 1,910 engineers and subscribe to the .NET Pulse newsletter. In the next issue, we'll compare structs vs ref structs. Subscribe: https://bit.ly/41QmmIF

٤٩

٧ تعليق