4 min read | By Admin | 15 September 2016 | Technology

  • share on:

With .NET Core 1.0 are available for .NET, the biggest changes since the .NET Framework 1.0. .NET is open source, not only runs on Windows but also on Linux and Mac, and can be used with small NuGet packages be developed much more agile.

NuGet packages that are already using the .NET Framework were introduced to enable faster updates as we are with the .NET Framework were accustomed. As .NET 1.0 was presented in 2000, it was still possible to update cycles of approximately two years. Today this is no longer possible, we want faster access to new features. With some areas of the .NET Framework is also already done so. The Entity Framework 6 is delivered completely from NuGet packages, also as System.Collections.immutable and System.Collections.Concurrent. However: functionality, already with the .NET Framework is installed on the system and the common language runtime can not be easily replaced in order to offer new features. These Administrator rights are necessary. The Entity Framework itself had suffered for many years that this framework partly with the .NET Framework has been installed on the system and additional classes on NuGet packages have come. There are some restrictions.

The .NET Core 1.0 is now all about NuGet Packages – also the runtime. This allows rapid innovation in all areas.

After applications now also the runtime is delivered to web applications which leads custom , I no longer have to wait for my provider the latest .NET version installed on the server.

The complexity of the .NET Framework

The .NET Framework is in the course of the years have become very complex. Many parts in the .NET Framework are also from libraries in new applications today is no longer required, e.g. .NET Remoting, LINQ to SQL, the old non-generic collection classes and much more. If you are in the last few years included with .NET, is the growing is less of a problem. Very good but it is a problem for new entrants in .NET. How should we decide which classes are to be used and which parts are no longer state of the art”?

After all parts of the .NET NuGet core now in smaller packages, is it possible to define reference packages. Developers can use this reference packages. It thus also defines which packages with the versions in the company will be used/May. This helps newcomers to take decisions and is not equal to the huge .NET Framework is to be seen.

Cross platform

Windows at all the various devices of various types and sizes – from the desktop and smartphone on the Hololens and IoT devices is nice. The actual dissemination but can not be ignored. On mobile devices have Android and iOS far larger market shares, and the Server Linux is widespread.

A big advantage of .NET Core 1.0 is something which has so far not been covered by .NET could be .NET on Linux and OS X – and even with support from Microsoft. It was exciting to see how rapidly the platforms have been added under Https://www.github.com/dotnet and virtually everything works the same way. A few years ago was still not conceivable. We have the core .NET on different platforms – and also the tools!

Open Source

.NET core – including the runtime, the C# compiler and the asp.net

MVC 6 – Now Open Source, has major advantages. You have now not equal even write extensions or bugs corrected. I am since early betas – so you can keep track of design decisions. Why some way or resolved, is easier to understand.

To extensions of C# 7 and even C# 8, it is now possible for example to give feedback and even the next versions of C# to influence. As mentioned: bug fixes need not even be made. I had several bugs reported on GitHub. But after just six days there was a fix in the daily builds.

.NET Core 1.0 is really a new world:

.NET code on different platforms, open source and in many small NuGet packages. .NET core is already in the first version of huge.

Comments are closed.

Join over 150,000+ subscribers who get our best digital insights, strategies and tips delivered straight to their inbox.