Why doesn't the AnyCPU build ship with the installer?

I'm curious to know why the AnyCPU build of LINQPad isn't the default version that ships with the installer.

It seems like it would be easier to only support and publish one build. Also I would generally hope for a small speed boost in native x64 code, thanks to the extra CPU registers.

But, it's very clear that you know what you're doing, so I assume there's a good reason for your choice of default. What are the advantages to having a 32-bit build be the default option for the "installer" version of LINQPad?


  • edited April 2013
    LINQPad in 32-bit mode can reference DLLs and EXEs built for X86 or AnyCPU.
    LINQPad in 64-bit mode can reference DLLs and EXEs built for X64 or AnyCPU.

    Most assemblies are built for X86 or AnyCPU. This makes the 32-bit version of LINQPad more versatile.

    The 32-bit version of LINQPad also uses less memory because references take half the space, although this is not so much of an issue on today's hardware.
Sign In or Register to comment.