The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Surprised that no one's told you to put a Cork in it.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment "Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst "I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
Was hunting around to figure out how to do a few things in 2017 that were fairly simple in previous versions. Turns out that the registry settings are handled differently now. Whilst searching for some insight on the old googley I came across this very useful posting:
Can anyone tell me how VS 2017 compares to VS 2015 as far as memory usage? I really like 2015, but am currently working mainly on a workstation with only 4GB memory and 2015 is a real memory hog, and painfully slow. (compared to 2010 at least)
I tried goggle, but all they talk about is load time improvements. Thanks!