Dot Net notes.
.Net core is a rework of .Net version 4, with leaner libraries. .NET Core vs ASP.NET Core Note: ASP.NET Core 3 and higher now depend on .NET Core and can no longer be used on .NET Framework.
Version history of .NET
- Version 1.0 - the initial version of ASP.NET, contemporaneously released alongside Visual Studio.NET.
- Version 1.1 - As the next significant version, 1.1 was released alongside Windows server 2003 and Visual Studio.NET 2003. Various supplemental features were added, such as the automatic validation of input as well as important mobile controls.
- Version 2.0 was released in tandem with Visual Web Developer Express, Visual Studio 2005 and SQL Server 2005. As a major release, it contained a plethora of additional features, such as GridView, FormView, and DetailsView data controls, alongside navigation and login controls, master pages, and a vast quantity of other additions. Notably, this version was the first to include the now crucial 64-bit processor support.
- Version 3.0 can be accurately surmised as a major release, including the consequential addition of several highly important features, such as the Windows Presentation Foundation (WPF), Windows Communication Foundation(WCF), Windows Workflow Foundation (WWF) and Windows Cardspace (WC).
- Version 3.5 came to us along with Windows Server 2008 and Visual Studio 2008. At this time, Microsoft provided several new features, of which the most salient were ListView data controls, DataPager controls, not to mention WCF support and LINQ.
- Version 4.0 – This was the version that preceded .NET 4.5. It was released in tandem with several parallel extensions. Unsurprisingly, as a major point release, many exceedingly high-utility features were introduced, such as Web Deployment, ADO.NET, Dynamic data and an innumerable list of others.
- ASP.NET Core 2.x, 1.x - ASP.NET Core is a redesign of ASP.NET 4.x, with architectural changes that result in a leaner, more modular framework.
Reference: https://www.accuwebhosting.com/web-hosting/asp-net-hosting
[Source code of .NET]https://referencesource.microsoft.com/ [.NET API directory]https://apisof.net/
The writing is kind of on the wall already. Microsoft wants user to migrate tool from .NET to .NET core, and it is the future.
https://gorillalogic.com/blog/what-why-and-how-to-migrate-to-net-core/ https://www.taithienbo.com/target-net-standard-when-building-shared-project-or-library-in-net/ .NET core source code
ASP.NET web from --> ASP.NET core blazor ASP.NET MVC --> ASP.NET core Classic ASP. https://edi.wang/post/2019/7/17/run-classic-asp-on-windows-10-and-azure-app-service https://blog.inedo.com/dotnet/net5-release-prep
- csc.exe -- compiler
csc.exe /platform:x86 /nologo /out:"~0.exe" %0
- ilasm.exe --
ilasm.exe /out yourexe.exe
- csc.exe is inside the C:\Windows\Microsoft.NET\Framework, and look for the specific version.
asp.net empty template. Keeping things simple.
https://www.c-sharpcorner.com/article/setting-up-mvc-core-3-0-application-with-empty-template/ https://dzone.com/articles/setting-up-an-mvc-core-31-application-with-an-empt https://docs.servicestack.net/templates-aspnet-empty
.NET based code is managed code, while windows API are unmanaged code. use PInvoke to call them
Embedding DLLs in a compiled executable
- Convert code from VB.NET to C# and vice versa using Roslyn
- https://corgibytes.com/blog/2018/09/11/converting-large-vb-to-csharp/
- softwaremeadows.com/posts/vbnet-windows-project-to-c-conversion/