Technology

In the competitive landscape of software development, performance is a crucial factor that can make or break the success of your .NET applications. Whether you’re building enterprise-level web applications, APIs, or microservices, optimizing performance is essential for delivering a seamless user experience and maintaining competitiveness in the market. In this comprehensive guide, we’ll explore 15 best practices that can help you maximize the performance of your .NET applications, complete with detailed explanations and code examples. 1. Utilize Caching Caching is a fundamental technique for improving the performance of .NET applications by storing frequently accessed data in memory. This reduces the need to retrieve data from slower data sources such as databases. In .NET, you can leverage the MemoryCache class from the Microsoft.Extensions.Caching.Memory namespace. public class ProductController : ControllerBase { private readonly IMemoryCache _cache; private readonly IProductRepository _productRepository; public ProductController(IMemoryCache cache, IProductRepository productRepository) { _cache = cache; _productRepository = productRepository; } [HttpGet("{id}")] public IActionResult GetProduct(int id) { var cacheKey = $"Product_{id}"; if (!_cache.TryGetValue(cacheKey, out Product product)) { product = _productRepository.GetProduct(id); if (product != null) { // Cache for 10 minutes _cache.Set(cacheKey, product, TimeSpan.FromMinutes(10)); } } return Ok(product); } } In this example, the MemoryCache is used to store product data retrieved from the database. If the product is not found in the cache, it’s fetched from the database and then stored in the cache with an expiration time of 10 minutes. 2. Optimize Hot Code Paths Identify and optimize hot code paths, which are sections of code that are frequently executed and contribute significantly to the overall runtime of your application. By optimizing these paths, you can achieve noticeable performance improvements. public class OrderProcessor { public void ProcessOrder(Order order) { foreach (var item in order.Items) { // Optimize this section for performance } } } In this example, the ProcessOrder method represents a hot code path responsible for processing order details. It should be optimized for performance, possibly by using more efficient algorithms or data structures within the loop. 3. Use Asynchronous APIs Leverage asynchronous programming to handle multiple operations concurrently, improving scalability and responsiveness. Asynchronous APIs in .NET can be utilized using the async and await keywords. public async Task<IActionResult> GetDataAsync() { var data = await _dataService.GetDataAsync(); return Ok(data); } In this example, the GetDataAsync method asynchronously retrieves data from a service. This allows the application to continue executing other tasks while waiting for the data to be fetched. 4. Asynchronize Hot Code Paths Convert hot code paths to asynchronous operations to further enhance concurrency and responsiveness, especially in performance-critical sections of your code. public async Task ProcessOrdersAsync(List<Order> orders) { foreach (var order in orders) { // Asynchronously process each order await ProcessOrderAsync(order); } } private async Task ProcessOrderAsync(Order order) { // Asynchronously process order details await Task.Delay(100); // Example asynchronous operation } In performance-critical code paths, consider making asynchronous versions of methods to allow for non-blocking execution and improved concurrency. 5. Implement Pagination for Large Collections When dealing with large datasets, implement pagination to fetch data in smaller chunks, reducing memory consumption and improving performance. public IActionResult GetProducts(int page = 1, int pageSize = 10) { var products = _productRepository.GetProducts() .Skip((page - 1) * pageSize) .Take(pageSize) .ToList(); return Ok(products); } In this example, the GetProducts method retrieves a paginated list of products from the repository, allowing the client to request data in smaller chunks. 6. Prefer IAsyncEnumerable Use IAsyncEnumerable<T> for asynchronous enumeration of collections to prevent synchronous blocking and improve efficiency, especially with large datasets. public async IAsyncEnumerable<int> GetNumbersAsync() { for (int i = 0; i < 10; i++) { await Task.Delay(100); // Simulate asynchronous operation yield return i; } } 7. Cache Large Objects and Use ArrayPool Optimize memory usage by caching frequently used large objects and managing large arrays with ArrayPool<T>. public void ProcessLargeArray() { var largeArray = ArrayPool<int>.Shared.Rent(100000); // Process large array ArrayPool<int>.Shared.Return(largeArray); } 8. Optimize Data Access and I/O Minimize roundtrips and latency by optimizing data access and I/O operations, such as database queries and external API calls. public async Task<IActionResult> GetCachedDataAsync() { var cachedData = await _cache.GetOrCreateAsync("cached_data_key", async entry => { // Retrieve data from database or external service var data = await _dataService.GetDataAsync(); // Cache for 15 minutes entry.AbsoluteExpirationRelativeToNow = TimeSpan.FromMinutes(15); return data; }); return Ok(cachedData); } 9. Use HttpClientFactory Manage and pool HTTP connections efficiently with HttpClientFactory to improve performance when making HTTP requests. public async Task<IActionResult> GetRemoteDataAsync() { var client = _httpClientFactory.CreateClient(); var response = await client.GetAsync("https://api.example.com/data"); if (response.IsSuccessStatusCode) { var data = await response.Content.ReadAsStringAsync(); return Ok(data); } else { return StatusCode((int)response.StatusCode); } } 10. Profile and Optimize Middleware Components Profile and optimize frequently-called middleware components to minimize their impact on request processing time and overall application performance. // Example middleware component public class LoggingMiddleware { private readonly RequestDelegate _next; private readonly ILogger<LoggingMiddleware> _logger; public LoggingMiddleware(RequestDelegate next, ILogger<LoggingMiddleware> logger) { _next = next; _logger = logger; } public async Task Invoke(HttpContext context) { // Log request information _logger.LogInformation($"Request: {context.Request.Path}"); await _next(context); } } 11. Use Background Services for Long-Running Tasks Offload long-running tasks to background services to maintain application responsiveness and prevent blocking of the main application thread. public class EmailSenderService : BackgroundService { protected override async Task ExecuteAsync(CancellationToken stoppingToken) { while (!stoppingToken.IsCancellationRequested) { // Check for pending emails and send them await SendPendingEmailsAsync(); // Wait for some time before checking again await Task.Delay(TimeSpan.FromMinutes(5), stoppingToken); } } } 12. Compress Responses to Reduce Payload Sizes Enable response compression to reduce the size of HTTP responses, minimizing network bandwidth usage and improving overall application performance, especially for web applications. // Configure response compression in Startup.cs public void ConfigureServices(IServiceCollection services) { services.AddResponseCompression(options => { options.EnableForHttps = true; options.MimeTypes = new[] { "text/plain", "text/html", "application/json" }; }); } 13. Stay Updated with Latest ASP.NET Core Releases Ensure your application is up-to-date with the latest ASP.NET Core releases to leverage performance improvements and new features provided by the framework. 14. Avoid Concurrent Access to HttpContext Avoid concurrent access to HttpContext as it is not thread-safe. Access to HttpContext should be synchronized to prevent race conditions and ensure application stability. // Example usage in controller action public IActionResult GetUserData() { var userId = HttpContext.User.FindFirst(ClaimTypes.NameIdentifier)?.Value; // Retrieve user data using userId return Ok(userData); } 15. Handle HttpRequest.ContentLength Appropriately Handle scenarios where HttpRequest.ContentLength is null to ensure robustness and reliability in request processing, especially when dealing with incoming HTTP requests. // Example usage in controller action public async Task<IActionResult> ProcessFormDataAsync() { if (Request.ContentLength == null) { return BadRequest("Content length is not provided"); } // Process form data return Ok(); } By implementing these 15 best practices in your .NET applications, you can significantly enhance their performance, scalability, and user experience, enabling you to meet the demands of modern, high-performance software development. Remember, performance optimization is an ongoing process, so continuously monitor and refine your application to ensure it remains optimized for maximum efficiency.

How to Prevent Spam in Contact Forms with .NET Core 8.0 MVC – A Step-by-Step Guide Dealing with spam submissions in your lead or contact forms can be incredibly frustrating—especially when you’ve already implemented CAPTCHA and other spam prevention measures. But what if I told you there's a simple yet effective solution that could help you significantly reduce unwanted form submissions? In this post, I’ll walk you through a quick tip for blocking spam in your forms using .NET Core 8.0 MVC. While this solution is tailored to .NET Core, the logic can be adapted to other technologies as well, making it versatile and easy to implement across different platforms. Why Spam Forms Are a Problem Spammers often use automated bots or scripts to find and submit contact or lead forms on websites, flooding your inbox with irrelevant, sometimes harmful, content. CAPTCHA (Completely Automated Public Turing test to tell Computers and Humans Apart) has been a popular solution for this, but it’s not foolproof. Bots are becoming smarter and can sometimes bypass CAPTCHA mechanisms. Luckily, there’s a much simpler method to keep spammers out while ensuring legitimate visitors can still submit forms without a hitch. The Simple Trick: Adding a Hidden Field The solution? A hidden input field. It’s a basic technique that prevents bots from submitting forms, as they typically “fill out” all fields, including hidden ones. By checking if this field is empty when the form is submitted, you can easily determine whether it was filled out by a bot or a human. Let’s take a look at how to implement this in a .NET Core 8.0 MVC application. Step 1: Build the Contact Form Here’s a basic contact or lead form that users can fill out. This example uses .NET Core MVC syntax: <form asp-action="contact" asp-controller="home" method="post"> <input class="form-control" type="text" maxlength="255" asp-for="FullName" placeholder="Your Name" required> <input class="form-control" type="email" maxlength="255" asp-for="Email" placeholder="Your Email" required> <input class="form-control" type="text" pattern="^[0-9]*$" maxlength="15" asp-for="Phone" placeholder="Your Phone with Country Code"> <textarea class="form-control" asp-for="Message" cols="40" rows="5" maxlength="1000" placeholder="Your Message" required></textarea> </form> Now, let’s add a hidden field to this form: <input class="additional-note" type="text" style="display:none;"> Step 2: Implement the Spam Check Logic When the form is submitted, we check whether the hidden field is filled out. If it’s empty, the submission is likely from a human. If it's not, it’s probably a bot, and we can discard the submission. In the controller, add the logic to handle this check: [HttpPost("contact")] [ValidateReCaptcha] public async Task<IActionResult> Contact(LeadModel model) { if (!ModelState.IsValid) return View(); try { bool result = await _contactService.SaveLead(model); TempData["success"] = result ? "We have received your request, and we'll get back to you shortly!" : "Sorry, we couldn't process your request."; return RedirectToAction("contact", "home"); } catch (Exception ex) { TempData["fail"] = "Sorry! Something went wrong while processing your request."; _logger.LogError(ex, $"Error occurred while saving lead - {Helper.Dump(model)}"); } return View(); } Step 3: Business Logic Service In the business logic service, we need to ensure that the lead is saved only if the hidden field is empty (indicating it wasn’t filled out by a bot): public async Task<bool> SaveLead(LeadModel? leadModel) { if (leadModel == null || !string.IsNullOrWhiteSpace(leadModel.RepeatLead)) return false; // Discard leads where the hidden field is filled out (likely spam). var lead = _mapper.Map<Lead>(leadModel); return await _contactRepository.SaveLead(lead); } How It Works: Bots vs Humans: Bots usually fill out all fields, including hidden ones, whereas humans won’t interact with hidden fields. Quick Spam Detection: If the hidden field is filled out, we treat the submission as spam and reject it. Seamless User Experience: Legitimate users can still submit the form as usual without any interruption. Why This Works Spammers use automated scripts to find and submit forms, but they don’t know about hidden fields that are intentionally left blank. This simple trick helps filter out spam without adding extra layers of complexity or affecting user experience. Plus, it’s incredibly easy to implement with .NET Core MVC. Conclusion: A Simple Yet Effective Spam Prevention Solution Implementing a hidden field in your forms is a quick and effective way to fight spam without over-complicating things. This approach works across various technologies, so feel free to adapt it to your tech stack. By using this method, you can keep your contact forms clean and only receive genuine submissions. 💪 What Do You Think? Have you tried similar techniques to block spam in your forms? What methods have worked best for you? Share your thoughts in the comments below! Also, feel free to share this post with anyone who might benefit from a spam-free experience on their website. Let’s keep our forms secure and user-friendly!

🚀 C#/.NET Tip - Const vs Readonly 💡 💎 Understanding the Difference Between const and readonly in C# 🔹 Const: Constants are static by default. They must be assigned a value at compile-time. Can be declared within functions. Each assembly using them gets its own copy of the value. Can be used in attributes. 🔹 Readonly: Must be assigned a value by the time the constructor exits. Evaluated when the instance is created. Static readonly fields are evaluated when the class is first referenced. Example: public class MathConstants { public const double Pi = 3.14159; public readonly double GoldenRatio; public MathConstants() { GoldenRatio = (1 + Math.Sqrt(5)) / 2; } } Explanation: Pi is a const and its value is fixed at compile-time. It cannot be changed and is the same across all instances. 2. GoldenRatio is a readonly field, which is calculated at runtime when an instance of MathConstants is created. This allows for more flexibility as the value can be set in the constructor. This example highlights how const is used for values that are truly constant and known at compile-time, while readonly is used for values that are determined at runtime but should not change after being set. I hope this helps! 😊

In-memory caching stands as a cornerstone technique in optimizing the performance and scalability of ASP.NET Core applications. By storing frequently accessed data in memory, developers can drastically reduce the need to fetch information from slower data sources such as databases or external APIs. This leads to faster response times, improved resource utilization, and ultimately, a superior user experience. In this comprehensive guide, we’ll delve deep into the intricacies of in-memory caching, exploring its benefits, setup process, implementation strategies, and best practices. Understanding the Significance of In-Memory Caching: Accelerated Performance The primary advantage of in-memory caching lies in its ability to boost application performance. Retrieving data from memory is inherently faster than fetching it from disk or over the network. Consequently, in-memory caching significantly reduces latency, ensuring that users receive timely responses to their requests. Reduced Load on Data Sources By caching frequently accessed data, ASP.NET Core applications can alleviate the burden on external data sources, such as databases or web services. This reduction in load translates to improved scalability, as the application can handle more concurrent users without compromising performance. Enhanced User Experience In-memory caching contributes to an enhanced user experience by providing quick access to frequently requested information. Whether it’s product listings, user profiles, or dynamic content, caching ensures that data is readily available, resulting in a smoother and more responsive application interface. When to Use In-Memory Caching: While in-memory caching offers numerous benefits, it’s essential to use it judiciously and considerately. Here are some scenarios and considerations for leveraging in-memory caching effectively in ASP.NET Core applications: Frequently Accessed Data In-memory caching is most beneficial for data that is accessed frequently but changes infrequently. Examples include reference data, configuration settings, and static content. Caching such data in memory reduces the overhead of repeated database or file system accesses, leading to significant performance improvements. High-Volume Read Operations Applications with high-volume read operations, such as e-commerce platforms with product listings or content management systems with articles, can benefit greatly from in-memory caching. By caching frequently accessed data, these applications can handle large numbers of concurrent users while maintaining responsiveness and scalability. Expensive Computations or Queries In-memory caching can also be valuable for caching the results of expensive computations or database queries. By caching the computed or queried results, subsequent requests for the same data can be served quickly from memory, avoiding the need to repeat the costly operation. User Session Data For applications that store user-specific data during a session, such as shopping cart contents or user preferences, in-memory caching can provide a fast and efficient mechanism for managing session state. By caching session data in memory, the application can minimize latency and improve user experience. Temporary Data Storage In-memory caching can serve as a temporary data storage solution for transient data that doesn’t need to be persisted long-term. Examples include temporary authentication tokens, short-lived cache keys, or data used for the duration of a user session. Caching such data in memory can help reduce database load and improve application performance. Setting Up In-Memory Caching in ASP.NET Core: Configuring Services Enabling in-memory caching in an ASP.NET Core application begins with configuring the necessary services. This can be achieved in the Startup.cs file within the ConfigureServices method. public void ConfigureServices(IServiceCollection services) { services.AddMemoryCache(); // Add caching services // Additional service configurations... } By invoking the AddMemoryCache() method, developers incorporate the essential caching services into the application’s service container. Injecting IMemoryCache To utilize in-memory caching within various components of the application, developers need to inject the IMemoryCache interface. This is typically done through constructor injection in controllers, services, or other relevant classes. using Microsoft.Extensions.Caching.Memory; public class ProductController : ControllerBase { private readonly IMemoryCache _cache; public ProductController(IMemoryCache cache) { _cache = cache; } // Controller actions... } Implementing In-Memory Caching Strategies: With in-memory caching configured and IMemoryCache injected into the application components, developers can proceed to implement caching logic tailored to their specific use cases. Let’s explore a detailed example of caching product data in an ASP.NET Core web API. Example: Caching Product Data Suppose we have an endpoint in our web API for retrieving product details by ID. We want to cache the product data to improve performance and reduce database load. [HttpGet("{id}")] public async Task<IActionResult> GetProduct(int id) { // Attempt to retrieve the product from the cache if (_cache.TryGetValue($"Product_{id}", out Product cachedProduct)) { return Ok(cachedProduct); // Return the cached product } // If not found in cache, fetch the product from the data source (e.g., database or external API) Product product = await _productService.GetProductById(id); if (product != null) { // Cache the product with an expiration time of 5 minutes _cache.Set($"Product_{id}", product, TimeSpan.FromMinutes(5)); return Ok(product); // Return the fetched product } else { return NotFound(); // Product not found } } In this example: We attempt to retrieve the product with the given ID from the cache using TryGetValue(). If the product is found in the cache, it’s returned directly from memory. If not found, we fetch the product from the data source (e.g., database or external API) and cache it using Set() with an expiration time of 5 minutes. Syntax Examples: Here are examples of syntax for adding, removing, and other operations related to in-memory caching in ASP.NET Core using the IMemoryCache interface: Adding Data to Cache: _cache.Set("CacheKey", cachedData, TimeSpan.FromMinutes(10)); // Cache data with a key and expiration time Retrieving Data from Cache: if (_cache.TryGetValue("CacheKey", out CachedDataType cachedData)) { // Data found in cache, use cachedData } else { // Data not found in cache, fetch from source and cache it } Removing Data from Cache: _cache.Remove("CacheKey"); // Remove data from cache by key Clearing All Cached Data: _cache.Clear(); // Clear all data from cache Checking if Data Exists in Cache: if (_cache.TryGetValue("CacheKey", out CachedDataType cachedData)) { // Data exists in cache } else { // Data does not exist in cache } These syntax examples demonstrate how to perform common operations related to in-memory caching in ASP.NET Core using the IMemoryCache interface. From adding and retrieving data to removing entries and configuring cache options, developers can effectively utilize in-memory caching to optimize performance and enhance the user experience of their applications. Conclusion: In-memory caching represents a cornerstone technique for optimizing the performance and scalability of ASP.NET Core applications. By strategically caching frequently accessed data in memory, developers can minimize latency, reduce load on data sources, and deliver a superior user experience. Armed with a solid understanding of in-memory caching concepts and implementation strategies, developers can leverage this powerful tool to build high-performing and responsive applications that meet the demands of modern users.   Original Article - Mastering In-Memory Caching in ASP.NET Core

Ever heard of the Zip method in LINQ? It's a powerful tool for merging sequences, and it's something every developer should have in their toolkit. Let's dive into how this method can simplify your coding life, especially with the enhancements introduced in .NET 6. What is the Zip Method? The Zip method in LINQ allows you to merge two or more sequences into one. Starting from .NET 6, you can combine up to three collections at once. The resulting sequence will match the length of the shortest collection, ensuring a neat and tidy merge. Why Use the Zip Method? Simplifies Code: The Zip method reduces the need for multiple foreach loops, making your code cleaner and more readable. Customizable Pairing: You can use a result selector to customize how the elements are paired together, giving you flexibility in how you merge your data. Efficiency: By merging sequences in a single step, you can improve the efficiency of your code. A Practical Example Let's look at a simple example using .NET Core: static void Main() { var numbers = new[] { 1, 2, 3 }; var words = new[] { "one", "two", "three" }; var zipped = numbers.Zip(words, (n, w) => $"{n} - {w}"); foreach (var item in zipped) { Console.WriteLine(item); } } In this example, we have two arrays: numbers and words. The Zip method combines these arrays into a single sequence where each element is a combination of an element from numbers and an element from words. The result is a sequence of strings like "1 - one", "2 - two", and "3 - three". Real-world Scenario Imagine you're working on a project that involves merging data from different sources, like combining sales figures with product names. The Zip method can be your go-to solution. It's like making a perfect masala chai, where each ingredient blends seamlessly to create something wonderful. Conclusion The Zip method in LINQ is a versatile and powerful tool that can make your coding tasks easier and more efficient. Whether you're working on a small project or a large-scale application, this method can help you merge sequences with ease. Feel free to share your thoughts in the comments below. If you found this post useful, follow me for more tech insights and don't hesitate to share this with your network! 🚀

Hey Mudmatter community! 👋 Are you looking to make your C# code more readable and maintainable? Named tuples might be just what you need! They allow you to create lightweight, self-descriptive data structures without the overhead of defining a full class. What are Named Tuples? Named tuples in C# provide a way to create a tuple with named fields, making your code more intuitive and easier to understand. Why Use Named Tuples? Readability: Named fields make it clear what each value represents. Convenience: No need to define a separate class or struct for simple data grouping. Immutability: Tuples are immutable by default, ensuring data integrity. Example - Traditional // Traditional tuple var person = ("John", "Doe", 30); // Named tuple var namedPerson = (FirstName: "John", LastName: "Doe", Age: 30); // Accessing named tuple fields Console.WriteLine($"First Name: {namedPerson.FirstName}"); Console.WriteLine($"Last Name: {namedPerson.LastName}"); Console.WriteLine($"Age: {namedPerson.Age}"); Benefits in Action, Improved Code Clarity: // Without named tuples var result = GetPerson(); Console.WriteLine($"Name: {result.Item1} {result.Item2}, Age: {result.Item3}"); // With named tuples var namedResult = GetNamedPerson(); Console.WriteLine($"Name: {namedResult.FirstName} {namedResult.LastName}, Age: {namedResult.Age}"); //Simplified Data Handling: // Method returning a named tuple (string FirstName, string LastName, int Age) GetNamedPerson() { return ("John", "Doe", 30); } Named tuples are a fantastic feature to enhance your C# projects. Give them a try and see how they can simplify your code! Happy coding! 💻✨

🚀 Exciting News for EF Core Users! 🚀 The latest version of Entity Framework Core (EF Core 7) introduces a powerful new feature: Bulk Update! This feature significantly enhances performance when updating multiple records in your database. Let's dive into how it works and see a sample in action. What is Bulk Update? Bulk Update allows you to perform update operations on multiple entities directly in the database without loading them into memory. This is achieved using the new ExecuteUpdate method, which can be a game-changer for applications dealing with large datasets. Why Use Bulk Update? Performance: Reduces the number of database round-trips. Efficiency: Updates multiple records in a single SQL statement. Simplicity: Cleaner and more readable code. Sample Code Here's a quick example to illustrate how you can use the Bulk Update feature: context.Products .Where(p => p.Price > 100) .ExecuteUpdate(p => p.SetProperty(p => p.Discount, 10) .SetProperty(p => p.LastUpdated, DateTime.Now)); Improved Performance: Executes a single SQL update statement. Reduced Memory Usage: No need to load entities into memory. Cleaner Code: More concise and easier to maintain. Conclusion The Bulk Update feature in EF Core 7 is a fantastic addition for developers looking to optimize their data operations. Give it a try and see the performance improvements in your applications!

🚀 Supercharge Your EF Core Performance with BulkInsertAsync! 🚀 Struggling with large data insertions in your .NET applications? EF Core’s BulkInsertAsync can be a game-changer. Just install EFCore.BulkExtensions from nuget. Here’s a quick guide to help you get started: Why Use BulkInsertAsync? 1. Efficiency: Inserts multiple records in a single database round trip. 2. Performance: Significantly reduces the time taken for bulk operations. 3. Simplicity: Easy to implement with minimal code changes. Example Let’s say we have a Student entity and we want to insert a large list of students into the database. using EFCore.BulkExtensions; using Microsoft.EntityFrameworkCore; using System.Collections.Generic; using System.Threading.Tasks; public class Student { public int StudentId { get; set; } public string FirstName { get; set; } public string LastName { get; set; } public string Branch { get; set; } } public class ApplicationDbContext : DbContext { public DbSet<Student> Students { get; set; } } public async Task BulkInsertStudentsAsync(List<Student> students) { using var context = new ApplicationDbContext(); await context.BulkInsertAsync(students); } EF Core SaveChangesAsync: 1,000 records: 18 ms 10,000 records: 203 ms 100,000 records: 2,129 ms EF Core BulkInsertAsync: 1,000 records: 8 ms 10,000 records: 76 ms 100,000 records: 742 ms1 With BulkInsertAsync, you can handle large data operations efficiently and keep your application running smoothly. Give it a try and see the difference!

🚀 Simplify Your API Calls with Refit in C# .NET Core! 🚀 Are you tired of writing boilerplate code for HTTP clients in your .NET Core applications? Meet Refit – a type-safe REST library that turns your API into a live interface! 🎉 With Refit, you can define your API endpoints using interfaces and attributes, making your code cleaner and more maintainable. Here’s a quick example: public interface IUsersApi { [Get("/users")] Task<IEnumerable<User>> GetUsersAsync(); [Get("/users/{id}")] Task<User> GetUserByIdAsync(int id); } var usersApi = RestService.For<IUsersApi>("https://lnkd.in/dn7QrR5D"); var users = await usersApi.GetUsersAsync();  

🚀 C# Clean Coding Practice 💡 🎯 Use Proper Naming Conventions Naming your variables, classes, and methods effectively is crucial for writing clean and maintainable code. Following coding conventions not only enhances readability but also serves several key purposes:   ✔ Ensures consistency in code layout, allowing readers to focus on the content, not formatting. ✔ Helps others (and yourself!) understand the code more quickly based on familiar patterns. ✔ Simplifies the process of copying, modifying, and maintaining code. ✔ Promotes adherence to C# best practices.   Check out the table below for standardized C# naming conventions to follow when writing code. Let's keep our code clean and efficient! 💻✨ Object Name Notation Can Be Plural Namespace name PascalCase Yes Class name PascalCase No Constructor name PascalCase No Method name PascalCase Yes Method arguments camelCase Yes Local variables camelCase Yes Constants name PascalCase No Field name Public PascalCase Yes Field name Private _camelCase Yes Properties name PascalCase Yes Interface IPascalCase Yes Enum type name PascalCase Yes