Technology keeps on updating and the best dot net tips are to remain upgraded with time and pace. Here we list the changes in .Net Core 2.0.
1] .NET Standard 2.0 Extended APIs & the Potential to Reference Full Framework Libraries
.NET Standard expands the set of available APIs to include several missing features. It now supports over 32,000 APIs. It is now easier to connect your code to a .NET Standard library without major changes in code.
One of the biggest issues with .NET Core was the absence of third party libraries. For instance, when 1.0 was released, the logging libraries like log4net were not available, but now it is.
But that was a problem if you wanted to deploy your app on Mac or Linux. You could have made use of .NET Core and targeted full .NET framework to avoid these issues.
.NET Standard 2.0 has summed up a new compatibility shim that enables any .NET Core app to reference any library of the full framework.
2] Detailed OS Support
One of the big successes with .NET Core is to be able to port across multiple operating systems that include desktops, servers, and even mobile. Microsoft and the community continue to amplify the support of .NET Core.
Linux is considered as a single operating system instead of different distributions. This is also true for Windows and macOS.
3] ASP.NET Core Razor Pages Are Something New
ASP.NET presently supports razor syntax based pages, called Razor Pages. You can now develop a razor view without a controller. Though, you can make a class that takes in from PageModel which is actually a controller and model class for that page
4] This Has AVisual Basic for .NET Core!
It’s news that Visual Beginners All-purpose Symbolic Instruction Code supports .NET Core. Though it is limited to developing class libraries and console application, more is coming sooner.
If you have missed the changes in .NET 1.1, here we bring you some highlights.
1) xproj Project Files substituted by New Version of csproj
One of the main differences with .NET Core was new project files. Visual Studio used xproj and project.json files instead of the conventional csproj. The format of new project file was very simple but didn’t work with some .NET tools like msbuild.
2) MSBuild Now Works
3) Visual Studio 2017 – Enhancements to Tools
When project.json is not there, then how to perform multi-targeting of frameworks and the VS UI around references and dependencies completely changed in VS 2017.
To perform multi targeting, you have to edit the csproj file manually and things can turn little weird. The fact is that if you are targeting one framework, you can do it within the project properties.
To mention, one big advantage of VS 2017 is its easiness to install.
To be successful in yours .Net career, try to enhance your skill set in Dot Net Course and improve yourself through Dot NET training programs. In this reference, CRB Tech Solutions, Pune could be of great help and support for you.
They offer an industry oriented program for the best Dot Net course. Stay connected to this space for more technical blogs and updates related to the world of Dot Net.