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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

[Post Event] Azure AI Connect, March 2025

By
On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.
Post a Comment
Read more