Skip to main content

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

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. 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. 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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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

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.51EF 6.0.2VS2013
It seems that there …

[Post-Event] Codecamp Conference Cluj-Napoca - Nov 19, 2016

Last day I was invited to another Codecamp Conference, that took place in Cluj-Napoca. Like other Codecamp Conferences, the event was very big, with more than 1.000 participants and 70 sessions. There were 10 tracks in parallel, so it was pretty hard to decide at  what session you want to join.
It was great to join this conference and I hope that you discovered something new during the conference.
At this event I talked about Azure IoT Hub and how we can use it to connect devices from the field. I had a lot of demos using Raspberry PI 3 and Simplelink SensorTag. Most of the samples were written in C++ and Node.JS and people were impressed that even if we are using Microsoft technologies, we are not limited to C# and .NET. World and Microsoft are changing so fast. Just looking and Azure IoT Hub and new features that were launched and I'm pressed (Jobs, Methods, Device Twin).
On backend my demos covered Stream Analytics, Event Hub, Azure Object Storage and DocumentDB.

Title:
What abo…