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

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

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP