Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 4
    One more thing to consider when deciding which platform target to use: if the target of the Startup project is Any CPU and you're runnning on a 64 bit OS, you lose the ability to Edit and continue while debugging. (You're effectively debugging a 64bit process). You could make the Startup project target x86 to circumvent this while debugging. (The assemblies referenced from the startup project may continue to target Any CPU. Commented Mar 6, 2013 at 11:27
  • 10
    @CristiDiaconescu With VS2013 Edit and continue is now possible Commented Nov 14, 2013 at 12:50
  • 2
    I think there should be some note here about whether the project is an application or a class library as setting the target bitness for the latter can impact its availability to consuming applications depending on the platform. I ran into this with an x86 library being consumed by an AnyCPU application where I had to set Prefer 32-bit to avoid a load error. Commented Sep 24, 2018 at 20:26
  • Related to this, I feel like there could be another option for bitness, either 32-bit or 64-bit (or 128-bit for the future, etc.), but if you don't care, there could be a 'nunya bitness' Commented Feb 5 at 23:38