Skip to main content

World is changing - .NET Native is here to stay! Sustained by .NET vNext, this is the features

By
Many years ago there was the COM hell. I used to work on a legacy project, where one of my colleges yell “This is DLL hell”.
Well, with the new .NET vNext (4.5.2) will change the face of the world. We could say that the history of programing is now changing. With the features from vNext and the new compiler called Roslyn you can do anything you want. For example you can change the compiler implementation, write your own compiler over it and many more.
The feature that impresses me the most was saw called .NET Native. Even if now we have support only for Windows Store, we should expect in the future to have support of this feature for all platforms.
So, what is .NET Native?
It is a new kind of compiler for .NET. The code is compiled directly to specific machine code. No more JIT and other layer of abstraction. You get what you need for your machine, extremely optimized for the specific hardware (X86, 64b, ARM). The existing CLR was optimized and refactored.
Yes, you have the C++ performance from an application that was written in C#. This is so cool. Keep in mind that this feature in combination with other new features from .NET vNext will change the way how we wrote code (M2M era).
Because the generated code is native code, that is already optimized for that specific hardware architecture, the performance is improved with around 60% and if I understood well, the memory footprint (can be) is reduced with ~30%.
Remark: The dynamic code execution, that already exist will not be removed. It will exist in parallel with the new one (.NET Native - static).
The new code that is generated doesn’t depend on the CLR that is installed on the machine. Because of this we don’t need the CLR when we run an application compiled as Native. Also, .NET is not required anymore on the client machines (we have a self-contained native compiled code in the end). Yes! Sounds good, first step to write in C# for any kind of platform and OS….. Sounds good.
 In this moment vNext team seems to be at Alpha version. I looking forward to a new release and support for desktop and server. Also, in the embedded area interesting things will happen.

Comments

  1. JoymonMay 21, 2014 at 3:39 AM

    Dont you think with .Net native, we are going back to the old days where there is no intermediate code and we had to bundle separate executable for different machines?
    Only thing MSFT did is they got some programmers in C# who cannot think about any other language.

    ReplyDelete
  2. Ovidiu CucuJune 3, 2014 at 1:47 PM

    Probably, the run-time performance will be improved a little bit. However, that's not enough.
    Once I had to deal with C++ code ported from Java by... Java programmers. It looked like Java with C++ syntax and was a (performance) disaster.
    Definitely, a program written in C# will never achieve the performance of a program well written in C++.

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more