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.
Microsoft are just as arrogant with VS ... that takes far too long to get right as well.
Just about every setting in VS is exportable to a file than can then be imported into another machine or into a newer version. I've been using such files since VS2008 and it's still saving me a lot of time getting my editor, code formatting, window layout preferences and such every time I set up a new development VM.
Better yet, you can export/import subsets of such settings - one file strictly for window layouts, another for code formatting settings, etc.
Or are you talking about something else altogether?
No, exactly that - but I didn't know you could do that. And if you can, then why the elephant doesn't MS do exactly that automatically when you install a new version? That's actually more annoying than not having the facility at all!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
The trouble with importing settings for any ms app is that they often decide that things have to work differently, so you end up with things freezing, giving unexpected results (which you may or may not notice), and shouting "Warning, Will Robinson! Warning! Warning!" for no apparent reason.
I wanna be a eunuchs developer! Pass me a bread knife!
YMMV then. All I know is that I first created 3 or 4 separate settings files to group them logically, and reused the same files in VS2008, 2010, 2012, 2013 and 2015. As far as I can tell, they never caused freezes or even warnings (and even if they did, the import process is a one-time operation).
I get far more problems using versions of VS that were upgraded in-place (something I've stopped doing altogether), than just bringing these exported settings files (which ultimately are just XML if I recall correctly) on new clean dev VMs whenever a new version of VS comes out.
I'm - regularly - at the office four days a week, so for years the company used my computer to quickly set up new ones by duplicating the disk... Once upon a time the technician mixed the disks and ruined mine by overwriting it with an empty one - on that occasion I took my time to re-install the environment... 8 days (two working weeks)... No one ever since touched my computer in my absence...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
I respect you for studying. I should be doing the same! I had worked 55 straight days on a project, the last being Saturday the 24th; so I have just been taking it easy. My sports team got destroyed last night, so it's been a heavy dose of You Tube since.