Updating intellisense hang consolidating spare part warehouses

We’re talking about same projects, different IDE here. A colleague told me “nah, you have to understand, all that RAM is because VS is now rendered with WPF”; I very much know that 3D acceleration needs shadow copies of GPU data in CPU ram due to how the hardware works, and that some rendering paths need more copies of the same data; but still I replied to him that I highly doubt that’s the reason; Visual Studio looks like is doing everything very inefficiently: for example when I switch between Release & Debug mode, it does not only take forever, disk activity fires like crazy, they’re obviously reparsing stuff they shouldn’t, the same must be happening with RAM consumption“. Not really, it was dead obvious without looking at a single line of VS’ source code.The fact that previous versions of the same IDE (and other competing IDEs) can switch instantly should’ve been a strong hint, but if you had any doubts Sysinternals’ Process Explorer is enough.

Not to mention VS2012 uses more RAM, which automatically means it can’t scale as well as the others will (it fights Moore’s Law).Also, let’s clear something out: I will only focus on C .Also, VS 2013 is still very new, so I will talk mostly about my experience with VS 2012.Autocomplete and highlighting are too, but a C programmer would trade those two for Go to Definition almost any day.Its most usefulness comes when examining other people’s code, and when refactoring (since it allows us to quickly navigate through the source files in the same flow the code does). When I’m refactoring and have to change a function (be its name, or its arguments), I need to change both the function definition and its forward declaration.

Search for updating intellisense hang:

updating intellisense hang-26updating intellisense hang-34

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating intellisense hang”