Please fix! Is it possible that Microsoft has fixed this internally and not for its customers? I cannot imagine a scenario where a Microsoft developer who has rights to the VS codebase hasn't found and fixed this bug yet, even if it is just for their own benefit.
Or perhaps there is a well-known work-around that Microsoft isn't sharing?
Happens to me a few times a day. The fix which is most likely to work is to delete the ".vs" folder associated with the solution. So the problem is probably related to corruption of those files. I suspect that in some variations of the bug there's a timing-related factor in play that makes it hard to repro.
I don't understand it but I love it. (I'll drink a couple beers later and then I'll surely be on the same page.)
This idea was moved here after it had started in the comments beneath another proposal: "Make the installation of Visual Studio light-weight and fast".
This idea is really nothing more than an extension of the work that Microsoft has started in the VS 2017 installer. *Please* avoid making negative or inflammatory remarks about winforms. This idea isn't to say that winforms is bad. It is only saying that winforms should be optional, since it isn't the only game in town anymore. A flame war will only slow things down, and may even prompt Microsoft to drag their feet on this idea.
Ctrl-z. Please vote on something important like 64 bit vs.
Yes, Microsoft, it *IS* necessary to make VS 64 bit.
If you want to force your internal users to run a 32 bit version of the app so they can find all your memory leaks for you, that is your business. But the rest of the world is sick and tired of the severe constraints imposed by 32 bit memory management.
For me it only takes about two hours of working before VS gets up above the 1.5 GB range or so. And afterwards, the app starts thrashing, sputtering, dragging, hanging, and performance becomes totally craptacular. You know it, I know it, everyone knows it. Just try something basic like unloading and reloading a project after VS has been open for a while. It is extremely painful.
Even IDE's like Eclipse have been supporting 64 bit memory for many, many years. Software developers often have 20 GB of RAM, and don't feel the desire to restart VS every hour after it reaches 1-2 GB.
Hello everyone and thank you for the feedback. We are actively investigating ways to improve how Visual Studio handles project content. This suggestion falls into that category. Unfortunately, we will not be able to address this feedback for the Visual Studio 2015 release. We will update the community when our plans in this area have gained more clarity.
Visual Studio – VS IDE Project and Build Team