I have been using Windows operating system from the beginning. When I first started using computer Windows XP was the latest operating system and it was amazing. After few years I started my career as a Java developer and in my office also I have been using Windows only.
 After few years Windows Vista got released and I suffered with it for few months and then Microsoft released Windows 7 which is the best Windows operating system IMO. And then they released Windows 8 which I don’t like much. Recently they released Windows 10 and I have upgraded from Windows 8.1 to Windows 10. Windows 10 is certainly better than Windows 8 but it still sucks compared to Windows 7. 

Big news: a new version of the NuGet clients has been released! This is version 3.3 of the client, with a new command-line and Visual Studio 2015 extension available for use. 

What's New in Blazor for .NET 8
Come find out about the future of Blazor in .NET 8! We'll explore all the upcoming features and improvements, including our effort to create a unified full stack web UI programming model that combines the strengths of client and server. We hope to see you there!

You will learn:
How Blazor is becoming the best option for full stack web development
How Blazor in .NET 8 will provide full flexibility to build web apps however works best for you
How to try out the latest Blazor features in .NET 8
 

The fourth preview of Entity Framework Core (EF Core) 8 is available on NuGet today!

Basic information

EF Core 8, or just EF8, is the successor to EF Core 7, and is scheduled for release in November 2023, at the same time as .NET 8.

EF8 previews currently target .NET 6, and can therefore be used with either .NET 6 (LTS) or .NET 7. This will likely be updated to .NET 8 as we near release.

EF8 will align with .NET 8 as a long-term support (LTS) release. See the .NET support policy for more information. 

Moq makes testing this piece of code a breeze. Without it, I would have had to write a whole lot of essentially throwaway code just to test this three line controller action. Probably one or two orders of magnitude more code. Clearly, this tool which I relied on heavily prior to .NET Core, remains quite a powerful weapon in my arsenal in .NET Core. 

Developed by Microsoft’s Research in Software Engineering, Code Contracts provide a way to convey code assumptions in your .NET applications. They can take the form of preconditions, postconditions, and state invariants. In C# Code Contracts Succinctly, author Dirk Strauss demonstrates how to use Code Contracts to validate logical correctness in code, how they can be integrated with abstract classes and interfaces, and even how they can be used to make writing documentation less painful.

The .NET 7 release marks an exciting milestone in many ways, but one in particular that’s exciting for ASP.NET developers building distributed apps or apps designed to be cloud native and ready for dynamic horizontal scale out is the addition of the Orleans team to the broader .NET team. Bringing Orleans and ASP.NET Core closer together has led to some exciting ideas for the future of how we blend Orleans into the ASP.NET toolchain, and coupled with the huge advances in performance throughout .NET 7 are improvements to Orleans 7 that bring over 150% improvements to some areas of the Orleans toolchain. This post will introduce you to some of the new features in Orleans 7. 

A simple yet organized project template for building ASP.NET Core APIs in .NET Core 3.1

Tools and Frameworks Used

• .NET Core 3.1
• ASP.NET Core - For building RESTful APIs
• Dapper - For data access.
• AutoMapper - For mapping entity models to DTOs.
• AutoWrapper - For handling request Exceptions and consistent HTTP response format.
• AutoWrapper.Server - For unwrapping the Result attribute from AutoWrapper's ApiResponse output.
• Swashbuckle.AspNetCore - For securing API documentation.
• FluentValidation.AspNetCore - For Model validations
• Serilog.AspNetCore - For logging capabilities
• IdentityServer4.AccessTokenValidation - For JWT Authentication handling
• Microsoft.Extensions.Http.Polly - For handling HttpClient Resilience and Transient fault-handling
• AspNetCoreRateLimit - For controlling the rate of requests that clients can make to an external API based on IP address or client ID.
• AspNetCore.Diagnostics.HealthChecks - For performing health checks
• Microsoft.AspNetCore.Diagnostics.HealthChecks - For getting the results of Health Checks in the application
• AspNetCore.HealthChecks.UI - For Health Status visualization
• xUnit and Moq - For unit testing.  

This article shows some of the ways in which localization can be used in a MVC 6 ASP.NET 5 application.

In this short video Rowan takes us through the process of using alternate keys in Entity Framework 7.