Before Visual Studio Community Edition : all those leftovers
-
Before the VStudio Community edition released you had to install 3 different VStudio products to get all of the project types. It was crazy. Finally, I installed VStudio 2013* Community which seemed to do everything but I never uninstalled all those other products. Now, I'm going through and uninstalling Visual Studio Express 2013 For Web Visual Studio Express 2013 for Windows Desktop Visual Studio Express 2013 for Windows (EDIT: uninstall has been running for 20 minutes still not done) Can't believe how slow the uninstall is. I'm glad Microsoft finally brought these all back together again. *I know, Community 2015 is available, but that's another crazy thing. Looks like you can't upgrade 2013, but you have to uinstall and install 2015 seperately.
I expect that still doesn't include SSDT and SSDTBI -- correct me if I'm wrong. Regardless, why would anyone want "everything"? At work, I have VS 2012 Ultimate. I do only a very small amount of WinForms development in C#. I mostly do SSIS, which means adding SSDTBI. Also we use TFS. Everything else included in VS Ultimate is wasted on me. I could probably use VS Express with SSDTBI and access TFS only through the command line and Shell Extensions (or whatever they're called) -- I already have my own console utilities to do certain things in TFS via the API.
-
I just looked for a project using WiX installer and couldn't find anything in community 2015. Maybe there is some way to get it but it doesn't look like it from my initial search. Also, I can't tell if it's native 64 bit version or not. Installed on a 2014 R2 server 64 bit vm but I just can't tell if Community 2015 is true 64 bit or not. Very difficult to tell. Looks like it is installed under Program Files (x86) though. I built a winform as 64 bit and tried debugging and it allowed it so maybe that is fixed, not sure.
Thanks for your response. To add WiX functionality in the past, you needed at least the Pro version of VS. That probably still applies - A pity. I don't think any versions of VS are native 64bit apps. Yes, they can build 64 bit apps, but the VS engines themselves have always been 32 bit.
How do we preserve the wisdom men will need, when their violent passions are spent? - The Lost Horizon
-
Ok, I am curious: Can you add plugins like the Windows Installer XML (WiX) to the Community Edition? What about Microsoft's Ribbon plug-in? I have no use for it, if the answer is negative. I suppose the 2015 versions of VS are still native 32bit apps, not 64? Later edit: See this thread: [^]
How do we preserve the wisdom men will need, when their violent passions are spent? - The Lost Horizon
Probably, it's close to the same as Professional, most obvious difference is the omission of TFS support. Comparison chart here[^].
Wrong is evil and must be defeated. - Jeff Ello
-
Before the VStudio Community edition released you had to install 3 different VStudio products to get all of the project types. It was crazy. Finally, I installed VStudio 2013* Community which seemed to do everything but I never uninstalled all those other products. Now, I'm going through and uninstalling Visual Studio Express 2013 For Web Visual Studio Express 2013 for Windows Desktop Visual Studio Express 2013 for Windows (EDIT: uninstall has been running for 20 minutes still not done) Can't believe how slow the uninstall is. I'm glad Microsoft finally brought these all back together again. *I know, Community 2015 is available, but that's another crazy thing. Looks like you can't upgrade 2013, but you have to uinstall and install 2015 seperately.
-
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.
-
Probably, it's close to the same as Professional, most obvious difference is the omission of TFS support. Comparison chart here[^].
Wrong is evil and must be defeated. - Jeff Ello
I cannot find any reference to the Windows Installer on the chart. I have also tried Google, but cannot find a direct answer to my simple question: "Can I add the Windows Installer XML (Wix) to the Community Edition of Visual Studio 2015?" If any one knows the answer, please let us know. It's kind of important to me. In previous versions of VS you had to have at least the Pro version for this plug-in. I do not want to go through the whole rigmarole of installing VS 2015 Community Edition, just to find that I cannot have WiX!
How do we preserve the wisdom men will need, when their violent passions are spent? - The Lost Horizon
-
Before the VStudio Community edition released you had to install 3 different VStudio products to get all of the project types. It was crazy. Finally, I installed VStudio 2013* Community which seemed to do everything but I never uninstalled all those other products. Now, I'm going through and uninstalling Visual Studio Express 2013 For Web Visual Studio Express 2013 for Windows Desktop Visual Studio Express 2013 for Windows (EDIT: uninstall has been running for 20 minutes still not done) Can't believe how slow the uninstall is. I'm glad Microsoft finally brought these all back together again. *I know, Community 2015 is available, but that's another crazy thing. Looks like you can't upgrade 2013, but you have to uinstall and install 2015 seperately.
-
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 :mad:
Press F1 for help or google it. Greetings from Germany
-
Before the VStudio Community edition released you had to install 3 different VStudio products to get all of the project types. It was crazy. Finally, I installed VStudio 2013* Community which seemed to do everything but I never uninstalled all those other products. Now, I'm going through and uninstalling Visual Studio Express 2013 For Web Visual Studio Express 2013 for Windows Desktop Visual Studio Express 2013 for Windows (EDIT: uninstall has been running for 20 minutes still not done) Can't believe how slow the uninstall is. I'm glad Microsoft finally brought these all back together again. *I know, Community 2015 is available, but that's another crazy thing. Looks like you can't upgrade 2013, but you have to uinstall and install 2015 seperately.
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.
-
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 :mad:
Press F1 for help or google it. Greetings from Germany
-
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. :D
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.
Wrong is evil and must be defeated. - Jeff Ello
-
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.
Wrong is evil and must be defeated. - Jeff Ello
-
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.
-
Thanks for your response. To add WiX functionality in the past, you needed at least the Pro version of VS. That probably still applies - A pity. I don't think any versions of VS are native 64bit apps. Yes, they can build 64 bit apps, but the VS engines themselves have always been 32 bit.
How do we preserve the wisdom men will need, when their violent passions are spent? - The Lost Horizon
Use SharpDevelop to Create and Compile your WIX projects.
-
Before the VStudio Community edition released you had to install 3 different VStudio products to get all of the project types. It was crazy. Finally, I installed VStudio 2013* Community which seemed to do everything but I never uninstalled all those other products. Now, I'm going through and uninstalling Visual Studio Express 2013 For Web Visual Studio Express 2013 for Windows Desktop Visual Studio Express 2013 for Windows (EDIT: uninstall has been running for 20 minutes still not done) Can't believe how slow the uninstall is. I'm glad Microsoft finally brought these all back together again. *I know, Community 2015 is available, but that's another crazy thing. Looks like you can't upgrade 2013, but you have to uinstall and install 2015 seperately.
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).
-
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.
-
I expect that still doesn't include SSDT and SSDTBI -- correct me if I'm wrong. Regardless, why would anyone want "everything"? At work, I have VS 2012 Ultimate. I do only a very small amount of WinForms development in C#. I mostly do SSIS, which means adding SSDTBI. Also we use TFS. Everything else included in VS Ultimate is wasted on me. I could probably use VS Express with SSDTBI and access TFS only through the command line and Shell Extensions (or whatever they're called) -- I already have my own console utilities to do certain things in TFS via the API.
SQL Server Data Tools in Visual Studio 2015[^]:
You must have an existing install of Visual Studio 2015 Professional, Enterprise, Express for Web, Express for Desktop or Express for Windows 10 to apply this update.
Doesn't mention Community edition, but if it works in Pro, then it works in Community. SSDT-BI for Visual Studio 2015 isn't out yet. It's expected some time after SQL Server 2016 is released. Consider yourself corrected. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Thanks for your response. To add WiX functionality in the past, you needed at least the Pro version of VS. That probably still applies - A pity. I don't think any versions of VS are native 64bit apps. Yes, they can build 64 bit apps, but the VS engines themselves have always been 32 bit.
How do we preserve the wisdom men will need, when their violent passions are spent? - The Lost Horizon
-
SQL Server Data Tools in Visual Studio 2015[^]:
You must have an existing install of Visual Studio 2015 Professional, Enterprise, Express for Web, Express for Desktop or Express for Windows 10 to apply this update.
Doesn't mention Community edition, but if it works in Pro, then it works in Community. SSDT-BI for Visual Studio 2015 isn't out yet. It's expected some time after SQL Server 2016 is released. Consider yourself corrected. :)
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
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.
