Yes that’s correct. We don’t do anything different when you compile for AnyCPU
vs x64 in C# or VB.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Friday, November 25, 2016 11:13 AM
To: ozDotNet
Subject: Re: Target x86/x64
Old thread
>
> Old thread, but catching up with old posts, and no replies here.
>
> No, it won't. All it does is control a flag that goes into the exe header
> so the OS knows what size process to run it in.
>
>> Now that almost all desktop and server machines are running 64-bit
>> Windows, I want to know if
Old thread, but catching up with old posts, and no replies here.
No, it won't. All it does is control a flag that goes into the exe header
so the OS knows what size process to run it in. You can even change this
post-build if you want (corflags.exe).
Adding a native compilation step is another ma
Greg
Your thinking is somewhat echoed by Microsoft with their move to .NET Core
(https://www.microsoft.com/net/core#windows) and .NET Native
(https://msdn.microsoft.com/en-us/library/dn600165(v=vs.110).aspx). Essentially
there is a broader recognition that JIT’d apps are slow and that in order
