MSBUILD 2014, C# gets an ahead of time compiler to native code.
Paulo Pinto
pjmlp at progtools.org
Thu Apr 3 01:11:37 PDT 2014
On Thursday, 3 April 2014 at 07:40:11 UTC, Bienlein wrote:
> This is not really spectacular. The intermediate byte code
> generated by the C# compiler also in the past was transfered to
> machine code. But this was happening at start-up time and this
> way slowing down application start-up. The change MS now made
> is only about reducing start-up times. It will not mean a
> difference in execution speed. Actually, Java is in this way
> still ahead of .NET as it converts the JVM byte codes on the
> fly to maschine code and is able to make optimization at
> runtime as it observes at runtime what is happening (Hot Spot
> runtime optimization). C# "native" can't do that as it converts
> all the intermediate byte code in one run into maschine code.
>
>> Posting this as it has direct implications into D's adoption.
>
> I don't really see why. Again, AFAIKS it is only about reducing
> start-up times of C# apps and won't result in a general
> performance improvement.
There is now a FAQ.
http://msdn.microsoft.com/en-US/vstudio/dn642499.aspx
<quote>
However, apps will get deployed on end-user devices as fully
self-contained natively compiled code (when .NET Native enters
production), and will not have a dependency on the .NET Framework
on the target device/machine.</quote>
For the time being only Windows Store is supported as that is
what Microsoft is pushing a new app model.
--
Paulo
More information about the Digitalmars-d
mailing list