For numerous reasons, No.

Why is explained in this MSDN post.

First, from a performance perspective the pointers get larger, so data structures get larger, and the processor cache stays the same size. That basically results in a raw speed hit (your mileage may vary). So you start in a hole and you have to dig yourself out of that hole by using the extra memory above 4G to your advantage. In Visual Studio this can happen in some large solutions but I think a preferable thing to do is to just use less memory in the first place. Many of VS’s algorithms are amenable to this. Here’s an old article that discusses the performance issues at some length: https://learn.microsoft.com/archive/blogs/joshwil/should-i-choose-to-take-advantage-of-64-bit

Secondly, from a cost perspective, probably the shortest path to porting Visual Studio to 64 bit is to port most of it to managed code incrementally and then port the rest. The cost of a full port of that much native code is going to be quite high and of course all known extensions would break and we’d basically have to create a 64 bit ecosystem pretty much like you do for drivers. Ouch.

For anyone else in same/similar boat as me - I needed Visual Studio 2019 Community in 2024 - these two below options worked for me. Note - I have a feeling someday one or both of these solutions will stop working if MS disables them somehow - but they're still working as of 5/2024.

1) Get VS2019 Community Installer from MS website

As of today appears still available for download: https://docs.microsoft.com/nb-no/visualstudio/releases/2019/system-requirements

2) Powershell Method

Part 1: Just get the VS2019 installer

# A) Specify the download URL for the Visual Studio 2019 Community edition offline installer
$url = "https://aka.ms/vs/16/release/vs_community.exe"

# B) Specify the path where you want to save the downloaded installer
$outputPath = "C:\temp\vs_community.exe"

# C) Download the file using Invoke-WebRequest
Invoke-WebRequest -Uri $url -OutFile $outputPath

Part 2: Also get the Full Offline Installer

(This is meant to be done after Part 1 above. Note: I didn't really need this but started it and it seems to work)

# (Must be in same folder as vs_community.exe)
# A) Specify where to put *ALL* the files for the full offline installer (?)
$layoutOutputPath = "C:\temp\VS2019CommunityLayout"

# B) Start the (long?) download process
Start-Process -FilePath "vs_community.exe" -ArgumentList "--layout $layoutOutputPath" -Wait

(Shout out to this guy on Reddit for small installer tip)