After you install service pack 1 and the update for Vista, what are the appropriate hotfixes and patches to apply to bring Visual Studio 2005 to the most recent possible version?
I'm hoping for an ordered list of security updates and appropriate patches if possible.
Under normal circumstances I'd advise installing Visual Studio and all available service packs only - hotfixes are "quick fixes" for problems, which are then rolled into service packs when they have been thoroughly tested with all the other hotfixes in the service pack.
You shouldn't normally install a hotfix unless your copy of Visual Studio exhibits the specific problem that the hotfix addresses, and it is vital to you that the problem is fixed. (Because any hotfix may introduce further instability and bugs, there is no point installing it unless you know you need it)
You'll find a (hopefully) complete list here (near the bottom of the page) though, which may help you locate any hotfixes you feel are relevant.
Related
I have Visual Studio Community Edition 2015 installed on my drive D:.
I recently got a 1TB SSD for my C: drive and wanted to move VS to that drive. Long story shortened; it was a nightmare. Although I could uninstall VS, I could not get it to reinstall in any other location except for D:. After three days of trying, I gave up and reinstalled back to D:. I still could not get it to install correctly and some things are "damaged". Updates, etc. do not completely succeed because of the "damaged" module installation. I do not want to risk running the "Repair" option in the control panel again because that often makes it worse (damages more things); which leads to a several hour process of uninstalling & reinstalling. This question shows some of the installer/uninstaller problems: Installation errors in repair of Visual Studio 2015 Community Edition on Windows 10
I am now planning on reinstalling Windows 10 Pro in order to clean up this install.
I was planning on eventually getting Visual Studio Professional 2015.
Will I have similar problems upgrading from "Community Edition" to the "Professional" version?
I was hoping to open a dialog box, type in the license key and have the "Community Editon" become a "Professional" version. Is that possible or is a complete uninstall/reinstall how this upgrade would work?
(Disclaimer: I worked on Visual Studio 2015 including portions of the setup experience while at Microsoft)
It can, but it isn't as simple as entering an upgraded product key, you also need the media.
When you buy/license Visual Studio 2015 Professional or higher, you'll have access to the install media, usually an ISO file or vs_setup.exe web-downloader. Mount the ISO image and run Setup and you'll be prompted to upgrade (if I remember correctly). You cannot (to my knowledge) have a side-by-side install of Community and Professional Edition (unlike you can with the Express editions).
Personally I would just do a full uninstall of Community first, then a clean install of Professional - when I worked on the setup experience of VS2015 I logged a whole bunch of bugs that were experienced during in-version SKU upgrades (e.g. upgrading Community to Enterprise, then downgrading to Professional), such as project template item templates disappearing, etc. It wouldn't surprise me if these still caused issues - I don't think it's worth the risk.
Regarding Visual Studio 2017
Visual Studio 2017 now fully supports side-by-side installations of different SKUs (which is why the installation directory is %programfiles(x86)%\Microsoft Visual Studio 2017\Enterprise). So rather than doing an in-place upgrade from a lower SKU to a higher SKU, you install it as a separate install entirely. You'll need to manually move your settings and extensions over (or use the Microsoft Account-based settings synchronization feature).
I personally know that when your email address subscription has professional your VS install using that email if community will upgrade on it's own to Pro.
I'm having this question since a month and I'm not able to test it, so i want to ask here if someone have met this situation. Since there is no official release of the new Visual Studio 2015 and it's on RC now ,I'm interested in does someone know if VS 2015 and VS 2013 could work together? Will be the code "infected" if both sides commit something together? Thanks in advance!
In theory yes, in practice no (or at least your results may vary). VS is designed for side by side installations. For consultants it is very common to have multiple versions of VS installed to match the environment of the client.
That being said, RC is pre release software and bugs are to be expected. Nobody can guarantee you won't have problems. VS is a huge and complex codebase. Throw in the number of permutations of possible plugins and extensions as well as environment conditions and there is always a chance of breaking. Just because it didn't blow up on someone else's system doesn't mean you won't have problems.
When I installed VS 2015 CTP6 a few months ago it broke an install of VS 2013 on the same machine. VS 2015 CTP6 installed without error but trying to "login" (Microsoft's new annoying way to infect all software with a user login) hung and became unresponsive. Upon restart devenv.exe complained about corrupted user settings and even before I tried I had a bad feeling that VS 2013 blew up as well. I was right and it took a reinstall to get it working.
Now on the other hand I installed VS 2015 RC side by side on a machine with VS 2010, 2012 and 2013 without any issue. Does that mean you are guaranteed to not have a problem? Of course not. It is pre-release software. If this is a mission critical machine and you don't have the time to potentially spend a few hours reinstalling VS 2013 I would install it in a VM. If it isn't mission critical or you have the time to reinstall if necessary then roll the dice. Honestly you "should" be fine, the RC is pretty stable but you never know.
You should be fine - you'll be using an existing code-base and as long as you don't change the .NET version in the properties, it will compile the same.
However, if you do want to check out the new vNext solutions, you'd have to specifically select the project template in the new project wizard.
These projects are run on the new DNX runtime (which is still evolving and subject to change)
Side by Side. Visual Studio 2015 (even RC) works seamlessly side-by-side with Visual Studio 2013.
See BUILD 2015 News: Visual Studio Code, Visual Studio 2015 RC, Team Foundation Server 2015 RC, Visual Studio 2013 Update 5
or the official guide in the documentation
you might follow the links inside for details about how to configure the target language specific frameworks.
While I can find plenty of places that known issues are documented for beta releases and release candidates for Visual Studio 2010, I can't find anything for the release itself, and maybe it's just me but I don't see an easy way of querying connect to get a list of reported issues?
Is there a list of known issues for VS2010 RTM version?
They're in Section 2 of the the Visual Studio 2010 Readme - get the latest version from http://go.microsoft.com/fwlink/?LinkID=133421
Today I had to reinstall. I used to have some hotfixes installed for VS2008 but no longer have them and can't remember why they were necessary. I'm expecting any security-related hotfixes to come through Microsoft Update, but I'm interested in VS bug fixes.
Does anyone have a list of hotfixes that they recommend installing for Visual Studio 2008 SP1?
You can find them all here:
http://kbalertz.com/Technology_639.aspx
Look for the ones with a "FIX" prefix.
Update: This is another good source of information about VS2008 updates.
http://code.msdn.microsoft.com/Project/ProjectDirectory.aspx?TagName=Visual%20Studio%202008&ProjectSearchText=Hotfix
Suggested hotfixes (links updated 4/2015):
KB957912 - Update for Visual Studio 2008 SP1 Debugging and Breakpoints
KB958502 - JScript Editor support for “-vsdoc.js” IntelliSense doc. files
KB960075 - VS Dev Environment crash after undocking windows or changing layouts
If connecting to TFS 2010:
KB974558 - Forward Compatibility Update
KB980216 - Error message when running unit tests with Forward Compatibility Update installed
Complete list of VS 2008 hotfixes (including TFS).
I recently rebuilt my machine. After installing Visual Studio 2008 and SP1 I was wondering about the same thing. In the end I used Windows update to check for updates and it found the following updates:
KB2465361
KB971092
KB72222
KB973675
Screen shot:
http://i.stack.imgur.com/yFf8H.png
All the VS2008 hotfixes are posted in the MSDN Code Gallery. You can search for tags "Visual Studio 2008" and "Hotfixes". You should only install the ones for problems you are actually having. Read through them and decide which ones you need. I would sort them by release date and install from older ones first. Also notice that some are included in other updates, such are the WPF designer hotfix included with the Silverlight tools.
I'm using Microsoft Connect - Visual Studio and .NET Framework as a source of updates for:
.NET 2.0+
VS2008
VS2010
I generally go with the ones that are pushed though Microsoft Update.
I thought that you can get bug fixes though Microsoft Update too.
If they don't come down automatically go to the site and look through the "Software, Optional" ones (or in the "Developer Tools" section).
Select Custom at the first screen and then wait a few minutes while it does it's scan.
However, there aren't any showing for me at the moment so I can't say for sure.
I recently got a copy of Visual Studio Team System Suite 2008. I am currently running Visual Studio Professional 2008. I am sure others have done this migration in the past.
What problems, if any, did you encounter?
Should I first uninstall Pro?
What about existing add-ons, Code Rush, GhostDoc etc? Do I need to uninstall these? Will I need to reinstall in order to use them with Team System?
I would love to hear about any experiences you have had both good and bad.
We made the switch and encountered absolutely no problems. Well, the installation for the Team Foundation Server was a royal pain, but that's not what you asked about. As far as Visual Studio goes, no issues whatsoever.
You should uninstall the pro version first.
As for add-ons, I don't know for sure because we never used them, but I would assume that you would uninstall those, install VSTS, then reinstall the add-ins.