6 ms·

Before clicking the link I was going to joke, "But is it 64-bit yet?" So I was pleasantly surprised :D

malkia 5y ago
This ^^^ - Longest waiting for this to happen. Solves quite a lot of issues - from not having to support 32-bit for your own extensions, designer forms, etc. to have tests run in the IDE, to not have plugins/extensions all go IPC which is probably not without problems.
- ripley12 5y ago
  Amen. Latest related issue I've run into: Visual Studio ships its own 32-bit Git binary, and getting that to play nicely with the native Windows OpenSSH for Git authentication is... not fun. https://developercommunity.visualstudio.com/content/problem/338518/visual-studio-fails-to-find-native-openssh.html https://developercommunity.visualstudio.com/content/problem/...
conradev 5y ago
I hope this is one step closer to ARM64 support!
jgon 5y ago
At a previous job we were repeatedly running into memory pressure issues and had talked about converting to a 64-bit application on and off for years. It was something I had pushed for as we were doing increasingly baroque work-arounds and I was asked to do some work to estimate what it would take to convert over. Ultimately it was decided not to do so and one of the repeated reasons that was cited for why we shouldn't was "Visual Studio isn't 64-bit, why are we so worried!?" Suffice it to say, I found that reasoning pretty frustrating and I am curious to know what will happen now that VS can no longer be cited.
cptskippy 5y ago
Didn't they make a huge deal about explaining why 64 bit was a bad idea? > With a 64-bit Visual Studio on Windows, you can open, edit, run, and debug even the biggest and most complex solutions without running out of memory. > I find it really satisfying to watch this video of Visual Studio scaling up to use the additional memory that’s available to a 64-bit process as it opens a solution with 1,600 projects and ~300k files. I guess the popularity of Node.js finally broke them.
- codespin 5y ago
  The architect who was responsible for that has a recent blog post on it: https://ricomariani.medium.com/visual-studio-why-is-there-no-64-bit-version-yet-849abcf0e5ec https://ricomariani.medium.com/visual-studio-why-is-there-no...
  - mrec 5y ago
    N.B. recently reposted, but originally written in 2009.
- tanseydavid 5y ago
  >> Didn't they make a huge deal about explaining why 64 bit was a bad idea? Yes, they did. I remember very well multiple MS employees who were present at a conference I attended, explaining the counter-intuitive 'notion' that VS would be worse off in 64-bit. At the time it seemed it ridiculous to me.
- dariusj18 5y ago
  Seems to me the declared bad idea was for time/budget concerns, and only minorly because of technical concerns.
RachelF 5y ago
Most of your 32 bit extensions probably won't work on the 64 bit version. I'd wait a year or so before bug testing for Microsoft.
merb 5y ago
I'm not sure if the 64-bit thing solves anything. I mean I use rider with a 1,5gig heap and it is basically fast. visual studio was always slow and 64-bit probably won't change that.

This ^^^ - Longest waiting for this to happen. Solves quite a lot of issues - from not having to support 32-bit for your own extensions, designer forms, etc. to have tests run in the IDE, to not have plugins/extensions all go IPC which is probably not without problems.

ripley12 5y ago
Amen. Latest related issue I've run into: Visual Studio ships its own 32-bit Git binary, and getting that to play nicely with the native Windows OpenSSH for Git authentication is... not fun. https://developercommunity.visualstudio.com/content/problem/338518/visual-studio-fails-to-find-native-openssh.html https://developercommunity.visualstudio.com/content/problem/...

conradev 5y ago

I hope this is one step closer to ARM64 support!

jgon 5y ago

At a previous job we were repeatedly running into memory pressure issues and had talked about converting to a 64-bit application on and off for years. It was something I had pushed for as we were doing increasingly baroque work-arounds and I was asked to do some work to estimate what it would take to convert over. Ultimately it was decided not to do so and one of the repeated reasons that was cited for why we shouldn't was "Visual Studio isn't 64-bit, why are we so worried!?" Suffice it to say, I found that reasoning pretty frustrating and I am curious to know what will happen now that VS can no longer be cited.

cptskippy 5y ago

Didn't they make a huge deal about explaining why 64 bit was a bad idea? > With a 64-bit Visual Studio on Windows, you can open, edit, run, and debug even the biggest and most complex solutions without running out of memory. > I find it really satisfying to watch this video of Visual Studio scaling up to use the additional memory that’s available to a 64-bit process as it opens a solution with 1,600 projects and ~300k files. I guess the popularity of Node.js finally broke them.

codespin 5y ago
The architect who was responsible for that has a recent blog post on it: https://ricomariani.medium.com/visual-studio-why-is-there-no-64-bit-version-yet-849abcf0e5ec https://ricomariani.medium.com/visual-studio-why-is-there-no...
- mrec 5y ago
  N.B. recently reposted, but originally written in 2009.
tanseydavid 5y ago
>> Didn't they make a huge deal about explaining why 64 bit was a bad idea? Yes, they did. I remember very well multiple MS employees who were present at a conference I attended, explaining the counter-intuitive 'notion' that VS would be worse off in 64-bit. At the time it seemed it ridiculous to me.
dariusj18 5y ago
Seems to me the declared bad idea was for time/budget concerns, and only minorly because of technical concerns.

RachelF 5y ago

Most of your 32 bit extensions probably won't work on the 64 bit version. I'd wait a year or so before bug testing for Microsoft.

merb 5y ago

I'm not sure if the 64-bit thing solves anything. I mean I use rider with a 1,5gig heap and it is basically fast. visual studio was always slow and 64-bit probably won't change that.