With my last upgrade of the Zoo di 105 podcast from .NET Core 3.1 to .NET 6, I have also updated how code analysis is implemented in the project. In the previous versions of .NET Core, it was implemented via a NuGet package (initially Microsoft.CodeAnalysis.FxCopAnalyzers and then

Introduction When compiling very big UWP applications, you can get the following error: C:\Program Files (x86)\Microsoft SDKs\UWPNuGetPackages\microsoft.net.native.compiler\2.2.8-rel-28605-00\tools\Microsoft.NetNative.targets(801,5): error : ILT0014: Failed to compile interop source code. See the build log for error details. This is

Let's suppose you have a Asp.Net Core application and you want to split the controllers in different class libraries (for example, to place the API controllers in a separate project, but another case could be when you may want to partition by areas). The MVC runtime won't automatically pick

In .NET Core, differently from .NET Framework, both Package and Project Dependencies are Transitive by default. Let's suppose for example to have the following project structure: Project DAL: it references the Json.NET NuGet package and defines the class ClassDB; Project BLL: it references the DAL project; Project UI: it

Code Analysis (formerly FxCop) is a very powerful tool to help improving the code quality in .NET projects. Let's make a bit of history: the previous version of this tool (FxCop) worked analyzing the compiled assemblies, searching for pattern of improvable code, in different areas, like for example performance, globalization,

Doing multiple code reviews, I see that a recurring problem is the missing or wrong implementation of the IDisposable pattern. I try to explain it in this article. Let's try to recreate the pattern, considering all the requirements: correct behavior: automatic disposition with an using or try/finally clause; incorrect