The performance of c ++, the capacity of c ?! You can have both fish and bear's paw. net native first glance (a preliminary experience and comparison diagram have been added)

For Microsoft developers, every BUILD conference is worth looking forward. This is also a big surprise. In addition to the popular WP8.1 release, there is also a technology that will make developers excited:. NET NATIVE. Let's take a closer look at what it is.

 

 

Memory usage is small, and power consumption is also smallIt is suitable for devices with relatively small memory such as tablets.

 

Cloud CompilationThe developer provides. NET code, and the consumer installs the machine code that can be used by the device.

.. NET version management. This is the most common problem during development. NET is not supported in earlier versions, or we need to support some low-version machines. As a result, our development environment is always carried out in earlier versions. net .. Net native compiled into machine code. I personally think this isItsBusiness Value.

According to the official website, windows Store programs compiled with native speed up by 60% and memory usage reduced by nearly 20%.

Supports windows store appsAnd does not support other. net desktop programs, such as WPF. However, we can expect an era in which all data is supported in the future. I personally think that WPF is difficult. After all, it uses GPU.

Forced my 64G Sophie PRO) And. net native. Later, we will develop some translations of. net native and foreign blogs.

 

After using. net native. Remove the file size that can be deployed after the. net native webpage Folder:

 

It is much smaller after compilation. For the first time, you may not be familiar with the files and deployment. Wrong !.

A more detailed evaluation will be provided later. Thank you for your continued attention!

 

This preview version only supports C # code because it is the. NET language used by most App Store applications. But after we broaden our work focus, there is no doubt that we will support all. NET languages.

True:. NET Native is not only related to performance, but also to productivity and consistent device experience. With. NET Native, you can write code in a hosting language and upload MSIL packages as usual. However, the application is deployed on the End User device as fully self-contained Native compilation code (when. NET Native enters production) and does not rely on the. NET Framework on the target device/computer. As you know, the. NET application has a wide range. Therefore, we have made significant investment in the complete. NET Framework (for example, we just released the CTP of RyuJIT ).

The solution we have considered is the application store application for devices-enabling developers to maintain. NET and MSIL productivity advantages and the ability to upload MSIL packages to the App Store, provide end users with local code with similar performance (C ++) (similar to Windows Phone 8, compile in the cloud ).

. NET Native currently focuses on Windows App Store applications. Micro Framework is delivered by the Windows Embedded team, and the. NET team works with them to provide customers with the best service.

You can create a common class library that is used with. NET Native. In this preview, only Windows App Store applications can be created using. NET Native. Using. NET Native to develop Windows Phone applications.

Yes .. NET Native compiler shares some basic code with Microsoft C ++ optimizer.

Desktop applications are an important part of our policy. Initially, we focused on Windows App Store applications and. NET Native. In the long run, we will continue to improve native compilation for all. NET applications.

Yes, the Framework Code will be compiled into the application. The package size is not significantly different because most App Store applications have a large number of multimedia resources. Therefore, the code size does change. However, only the framework used by the application is linked to the application. The final result is that the binary file compiled using. NET Native is in the same size range as the binary file running NGEN. We will continue to study strategies that further reduce the size difference.

Standard MSIL/JIT development experience in Visual Studio is used for general application development. The. NET Native compiler is called only when the application is deployed to the device. After most development processes are completed, the focus will be shifted to application optimization. At this time, the Compilation Time is similar to that of using the link time code to generate the optimized C ++.

Even if binary files are compiled locally, we retain the benefits of hosted code type security (as well as garbage collection) and complete C # exception model. Exploitation. NET Native, we also greatly optimized the interoperability path-therefore, although P/Invoke is not optimized for standard DLL calls, the overhead is extremely low to execute GC synchronization and any necessary messages.

. NET Native will support all functions supported by the target platform when it enters production. This is a preview version and many features are under development. Therefore, there are some restrictions. However, this preview supports open generics and reflection (yes, or even static compilation !). In this preview, the compiler has a built-in inspiration mechanism to find out the generic instantiation and metadata needed during runtime. Therefore, a large number of applications are expectedRun directlyWithout simplifying the source code to get the benefits of the compiler.

The service mode of the application remains unchanged. For the framework, the latest mode of. NET is to automatically provide library updates. We will continue to explore options; we look forward to hearing your suggestions and comments.

Yes; In this preview, developers can declare that a method (or type) is used, even if it is not called directly (please refer to the runtime instruction documentation ).

Http://msdn.microsoft.com/en-US/vstudio/dotnetnative

Http://blogs.msdn.com/ B /dotnet/archive/2014/04/02/announcing-net-native-preview.aspx

Http://channel9.msdn.com/Shows/Going+Deep/Inside-NET-Native