|
Richard Deeming wrote: Consider yourself corrected
No, I thought the OP was saying that Community came with everything already included. So I'll consider my argument supported.
|
|
|
|
|
You trust the various VS uninstallers to properly clean up after themselves?
All the different versions of VS I still need to hang on to go in a separate VM. Cleanup doesn't get any easier than that.
|
|
|
|
|
You are so right.
They are still uninstalling --- and it doesn't give me the feeling that they're going to clean themselves off properly. Ugh!
|
|
|
|
|
In my company I have an old PC which is now surviving the VS 2005, 2008, 2010 and 2012.
With all its "updates" and "service packs" it is a mess in the software settings
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
Your PC is 10 or more years old? I suggest you talk to your boss about a new machine!
How do we preserve the wisdom men will need,
when their violent passions are spent?
- The Lost Horizon
|
|
|
|
|
My PC's only 3 years old; but I have versions of VS as old as 03 installed on it. I've got 03, 08, 10, 12, and 15.
My next PC here definitely won't have 08 or 12 since I've upgraded everything I care about that was done on it to 2010 solutions and never used 2012 in production. I might be able to get rid of 2010 too by upgrading all my solutions again to 2015.
I'll still need 03 for regression checking though; the version of the app build in that uses a custom grid that won't compile to newer versions of the framework. (Not sure why, I spent about a day trying to make it work in 08 (05?) years ago before cutting my losses and porting to the new far less sucky .net 2.x datagridview class.)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I know. Unfortunately, it all becomes a huge mess.
Maybe that's Microsoft's "upgrade" plan.
|
|
|
|
|
can't upgrade 2013, but you have to uinstall and install 2015 seperately
That's not true. You can't upgrade vs2013 to vs2015 neither do you have to uninstall vs2013 to install vs2015. They are totally separate products. Same with older version. They work parallelly without interference.
|
|
|
|
|
right. separate products.
Imagine if your web browser were the same way.
You'd have 629 versions of Chrome on your machine.
|
|
|
|
|
Separate products, yes.
Common dependencies, also true.
Plenty of common settings in the registry? Take a guess.
Do you think there exists any third party dependencies that does not work with both versions at the same time?
So while you really can have several versions on your computer, the older ones tend to not work as advertised anymore IMHO. The new ones neither now that I think of it.
My recommendation would always be a reinstall of the computer if you want to have a newer version of VS.
|
|
|
|
|
That's what I thought too.
That's why it doesn't entirely make sense that when you go to install a newer version that Microsoft's installer doesn't ask you if you want to remove the old version or something.
|
|
|
|
|
They are separate products, you may not have value in the old version after an upgrade but many other people do.
In C++, each version of VS comes with a huge set of libraries that are vastly different from each other. The libraries are part of the VS installation, not some shared common library. This is good for backwards compatibility etc.
Such as how VS2012 comes with an early implementation of C++11, while VS2015 comes with a C++11/14 almost complete.
Also the compilers are different in each version, and having separate versions on your machines allow you to compile for each one.
In Web development or something a lot of people may not care about previous versions, but VS is an IDE that caters to "most" developers, and upgrading over a previous install isn't always appropriate.
And finally VS2015 fixes most issues mentioned in this post, on installation almost every major feature is now option to set to install. Installing C++ support can be disabled in VS2015 so the install size is gigabytes smaller than before.
|
|
|
|
|
Interesting. Thanks for posting.
|
|
|
|
|
NB: Make sure you check the Usage section: [^]
Community can't be used for commercial software; only individual use, charity/education, or open source work (or in small (<250 employees) companies, five developers can use it).
|
|
|
|
|
A word of warning:
I've installed VS 2015 community a couple of months ago for trial purposes, with VS 2010 installed on the system. I had no problems, and could use either.
Now that we've decided to purchase VS 2015 Pro, I've uninstalled VS 2015. It appeared to work, although, as you noted, the uninstallation rocess took quite some time. (~10-15 minutes - I didn't really check)
Then I started VS 2010 again and loaded a solution: unfortunately, the solution wouldn't load: it claimed that a dependency, .NET 4.0 was missing! I checked program installations, but there still was a dotnet 4.0.1 installation that I could see! Even after restarting, dotnet 4.0 was still being shown. Yet VS 2010 kept complaining that it was missing: clearly, the VS 2015 uninstallation must have broken something, although it wasn't clear what.
To cut the long story short: it wasn't .NET 4.0 that was missing, it was the -NET Multi-targeting Pack - whatever that is supposed to be! I got it back by 'repairing' the VS 2010 installation.
tldr; You can install VS 2015 side by side with an earlier version, but if you ever uninstall it (or the previous version), you may need to repair the remaining installation(s).
On a sidenote: the solution in question is 100% C/C++ unmanaged code. no idea why there is any link to .Net at all...
GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)
|
|
|
|
|
That's a good and interesting post related to all these uninstall / install challenges.
I will keep it in mind. Thanks
|
|
|
|
|
Does anyone else go through this... my mother never keeps her cell phone on. She turns it off like it's a regular phone and when I want to call her I have to call the old land line first and tell her to turn her cell phone on. Then I can call that.
So tell me, does anyone else go through this?
Jeremy Falcon
|
|
|
|
|
Kinda wondering why, having called the land line, you don't just talk to her there and then!
I am not a number. I am a ... no, wait!
|
|
|
|
|
I do, but sometimes you gotta send your mom a picture over a text.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: sometimes you gotta
No, you don't.
|
|
|
|
|
Ah, I keep forgetting that when people say phone they don't mean phone. It's an age thing!
I am not a number. I am a ... no, wait!
|
|
|
|
|
Yeah man, if you can't play video games on it, then it's not a phone.
Jeremy Falcon
|
|
|
|
|
My parents use their cell phone only when they're out. I never call it unless they're visiting us.
|
|
|
|
|
PIEBALDconsult wrote: My parents use their cell phone only when they're out. It's the same thing with mine. She'll keep it on while at work too, but when home expect it to be off.
PIEBALDconsult wrote: I never call it unless they're visiting us. No comment. I'm sorta the same way... sorta. I'll call if I need something. Ya know, because I care.
Jeremy Falcon
|
|
|
|
|
Why call them if they're visiting? Why not just speak to them face to face?
/ravi
|
|
|
|