.Net native code compilation, aka static linking for the .net age. This feature is a LOOOOONG time coming, they should have had it available a decade ago.<p>P.S. Mark my words, this is going to be a huge deal. Especially since MS is acquiring Xamarin, which basically does the same thing, but for mobile platforms. With the ability to develop in .net languages and still deliver a plain-jane .exe that doesn't require jitting it'll open up a lot of new opportunities. Especially if they start targeting non-windows platforms like linux, iOS, and android with fully-baked tools. Imagine how much more popular C# would be if it wasn't tied to the Windows platform? And if you could choose whether or not you wanted to ship a small managed exe or a fat native exe that launched quickly?
There are rumors that Microsoft is considering the purchase of Xamarin [1]. And now Microsoft is now previewing their .NET AOT compiler for X64 and ARM. I see great things in C#/.NET's future in mobile and cross platform development.<p>On another note, I wonder if Microsoft addressed the inherent limitations of AOT in C# [2]. I wonder if it's a compile-time error, or if that segment of code is interpreted. I doubt it's interpreted, as that's a giant perf loss.<p>[1] <a href="http://www.wpcentral.com/microsoft-reportedly-considering-acquisition-xamarin" rel="nofollow">http://www.wpcentral.com/microsoft-reportedly-considering-ac...</a><p>[2] <a href="http://www.mono-project.com/AOT#Limitation:_Generic_Interface_Instantiation" rel="nofollow">http://www.mono-project.com/AOT#Limitation:_Generic_Interfac...</a>
Native compilation! This are great news.<p>Never got the point why Java and .NET adopted a VM approach, back in the days when we already had safe systems programming languages like Modula-2, Modula-3, Oberon, Ada, Delphi with AOT compilers on their canonical toolchains.
Looks like I'm going start reading up on C# again! It's been a good 4 years without touching .NET but these developments make my want to try a hand in mobile Windows 8 development.
This confirms to me that as a software agency we were right to stick with C# even when it was "uncool" and there were plenty of new kids on the block (I'm looking at you RoR).<p>There were a number of times when I wondered if we had backed the wrong horse in Microsoft but being able to gain traction on mobile development (assuming the Xamarin purchase goes ahead) and other changes such as native compilation makes me happy with stuck with them.