I only see x86 version in msdn downloads.
相关问题
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- Visual Studio 2019 - error MSB8020: The build tool
- 'System.Threading.ThreadAbortException' in
- Visual Studio 2010 randomly says the command line
相关文章
- How to show location of errors, references to memb
- Log4Net Multiple Projects
- How to track MongoDB requests from a console appli
- Compiling error in C++ project with C and C++ code
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- VSIX: execute code on VS startup
- Copy different file to output directory for releas
Rico Mariani basically says:
Because there isn't much need for the IDE to take advantage of the 64 bit benefits.
The Framework itself comes in 32 and 64 bit editions.
Which x64 benefits do you want the IDE to take advantage of?
I bet most of the work would be testing both editions and managing the code for both editions from a single codebase. This isn't how the IDE team has worked (multi-CPU-architecture) the entire time it has existed. They took the big bet on managed code in VS10, so I can see how they might not want to take on additional risk in that cycle.
If I was managing such a task I'd wait for a longer release cycle.
Update: I was wrong in thinking .NET 5 would be released with Win 8, but no. Instead we got .NET 4.5, then .NET 4.5.1 with Win 8.1. Many small, incremental releases with the shortened Windows release cycles.