A long while ago Scott Hanselman talked about PerfWatson. I've finally decided to install this extension in Visual Studio, but the extension no longer appears to be available for public-consumption (perform either a search or click on the appropriate link on the PerfWatson Monitor extension).
Is there an alternative to PerfWatson, or has it been completely phased out?
The PerfWatson extension is now available, and was updated on May 24th. The first paragraph says:
The Visual Studio team no longer collects PerfWatson reports for Visual Studio 2010. Your reports helped us to identify the issues affecting you most, and you can see improvements in Visual Studio 11 Beta. The PerfWatson extension is included in the VS11 Beta release. If you would like to use PerfWatson to automatically report on any responsiveness issues you are encountering, please download and try out the VS11 Beta.
Looks like it's no longer valuable.
Update July 2017
It appears that PerfWatson is available as a Visual Studio Extension for 2012, 2013, 2015, and 2017.
Paul Harrington appears to be a software engineer at Microsoft, but no idea if the extension's purpose remains the same.
Related
I am currently using Visual Studio 2015 for programming ASP.NET Core applications. I have the following questions regarding installing Visual Studio 2017:
What is considered to be best practice and/or cleanest method?
Should I install Visual Studio 2017 beside Visual Studio 2015?
Should I first uninstall Visual Studio 2015 and all .NET Core dependencies and then install Visual Studio 2017?
Are there any tools that would ensure a clean uninstall of Visual Studio 2015?
From page Visual Studio 2017 Platform Targeting and Compatibility
Compatibility with Previous Releases Installation
You can install and use Visual Studio 2017 alongside previous versions of Visual Studio, including Visual Studio 2015, Visual Studio 2013, and Visua Studio 2012.
So yes. you can install them without any problem.
VS 2013, VS 2015, and VS 2017 all work well side-by-side. VS 2012 can be a little dodgy on Windows 10, but should also work side-by-side. In theory VS 2010 should also work side-by-side with those, but I've run into quirks in the past with them interfering with one-another.
Projects should round-trip between 2015 and 2017 generally, although there are some one-way upgrade scenarios.
Note that if you really just need the older compiler toolset for some reason, you can also install VS 2017 and select the optional component Microsoft.VisualStudio.Component.VC.140 which installs the older v140 compiler which you can still use with the VS 2017 IDE. That said, there's not a lot of reason to do this since the VS 2015 & VS 2017 C++ standard libraries are binary compatible so you can mix them in a project.
See this blog post for information on VS 2017.
It sounds like you have done some projects in 2015 already, so you will probably want to keep it.
Once you open a project in a new version, it will try to upgrade the project and then you can't go back.
However, if you have multiple versions installed at the same time, when you try to open a project, say, from Windows Explorer, it will open it with the "Visual Studio Version Checker" and will look at the project file and determine which version to open it in.
Bottom line, if you have the hard drive space, there is no reason to not install them alongside each other.
In the past, it was recommended to install them in sequential order if you are installing multiple versions, but it doesn't sound like this is an issue for you and I don't know if that is even a problem anymore as it has been several versions since I have had to deal with that.
Good luck!
Personally, I would keep both - there have been multiple times through the years where you have compatibility issues and NEED to have the prior version(s). I've also had old project that will not upgrade and I've gone back and reinstalled old VS versions.
If you have no reason to keep VS2015 in your computer I would suggest uninstalling it.
I uninstalled VS2015 after installing VS2017 and later noticing that I was still using an old taskbar shortcut to VS2015.
So I was inadvertently still using VS2015.
Maybe some special cases require keeping older versions of VS along side the new version, but for the rest of us, I say, uninstall!
VS 2015 is the last version that is supported by Installshield LE.
If you have a need for building installers in the future, it will be useful to have VS 2015
1,2,3. Visual Studio 2017 has more features over 2015 and it contains 2015's current features so you don't need 2015 alongside 2017. Just stick with 2017. And I don't think you will have any problems while opening 2013 and 2015 projects with Visual Studio 2017.
Uninstall Tool is a good tool to use. It cleanses all the leftover files and registry entries after running the original uninstallation wizard and even tells you how many files will be cleaned after the required reboot.
For people continuing to read this, I have Visual Studio Professional 2008 (For Windows Embedded 6.5), 2010, 2015, 2017 and they all work even if open at the same time.
Edit: As stated in other answers, they need to be installed from oldest version to newest.
I'm trying to request a code review from another developer on a project hosted in Visual Studio Online using git.
I'm using Visual Studio 2015 Community Edition, which according to this Microsoft comparison page, supports code review (Under the "Collaboration Tools" heading).
Is this an option I need to turn on? I've looked in the Team Explorer panel, under the Project section and all I see is "Changes", "Branches", "Sync" and "Settings". From the videos I've watched, I expected to see "My Work" in that section too.
I had this problem also. Apparently My Work is only available in certain versions of Visual Studio:
My Work appears only when you have installed Visual Studio Premium or Visual Studio Ultimate.
Also, it won't show up for Git. Only for Team Foundation VC.
MSDN: Work in Team Explorer
Edit: I missed the link in the question, but looks like MS documentation might not be correct (surprise, surprise!) on one or the other. From that link it looks like there is not even a Premium or Ultimate version of 2015 offered. Very confusing. I'm guessing the page I referenced is not correct, even though it says it's for 2015. So I'd assume it's only available in Enterprise version, since in my own case, it did not show up in the Professional version.
I see this in the newly released VS 2015:
However, clicking it does nothing (tried also double-clicking, shouting at it, etc.). How to interact with this element?
It looks like they just released Resharper 9.1.2 today (July 21, 2015).
I had this same problem when I installed 9.1.1 Reshaper from Visual Studio 2015 in the Tools -> Extensions and Updates... menu.
It's likely best to just grab it on their site right now.
Ah, it's ReSharper 9.x causing this. They probably need to update for VS2015 RTM yet.
I have just installed VS 2013 RC2 and TypeScript refactoring stopped working. It disappeared from context menu, and pressing Ctrl+R, Ctrl+R gives the following error message:
The key combination (Ctrl+R, Ctrl+R) is bound to command (.Refactor.Rename) which is not currently available.
I have tried restarting VS, didn't help. Any ideas, workarounds?
Edit:
I have submitted a bug to Microsoft. Please upvote it if you have the same issue:
https://connect.microsoft.com/VisualStudio/feedback/details/860463/typescript-refactoring-stopped-working-in-vs-2013-rc2
Microsoft posted the following answer to my question on MS Connect. Seems that while refactor/rename was available in VS Express Edition with TypeScript 0.9, in TypeScript 1.0 it's only available from VS Pro upwards.
Posted by Microsoft on 19/05/2014 at 09:25
Thank you for reporting this issue.
Refactor/rename and NavigateTo are features that are found in the Pro+
versions of TypeScript in Visual Studio 2013. The Pro+ tools are aimed
at helping users work with larger codebases, so there is a focus on
building up tools to help support those codebases in those versions of
Visual Studio. We're working to continue to refine to make the
experience best across both Express and Pro+, with the right features
to help users who want to learn TypeScript and those who want to move
to using TypeScript in larger projects.
For me it happened because of resharper conflict. I uninstalled resharper and restarted visual studio
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.