3 ms·
Prefer 32-bit does nothing for modern .NET targets. This is actually the first time I've heard the term being used in many years, even back in .NET Framework 4.
by neonsunset 3y ago
Prefer 32-bit does nothing for modern .NET targets. This is actually the first time I've heard the term being used in many years, even back in .NET Framework 4.6.x days it wasn't much of a concern - the code would be executed with 64-bit runtime as a default on appropriate hosts.
- gfody 3y agothe 32bitpref corflag isn't part of a .net core target since those are always il, it is more properly a runtime concern as it should be it's still the default in .net as of 4.8.1 (has been since it was introduced in 4.5 roughly coinciding w/java's pointer compression feature which is also still the default today)
- neonsunset 3y agoThe .NET Framework target might as well not exist :D Many libraries are straight up dropping NS2.0 TFM and overall community tends to perceive the request to still target it very negatively. Sure, Visual Studio still runs some in-process features on top of it, and so do Office add-ins, but it's an active work-in-progress to get rid of any new code having to be written while still targeting it. So, in that regard, this setting does not matter.
- gfody 3y agoin .net core there's no setting, you target the x32 abi by choosing a runtime or target platform ending in "32" or "x86"