Open the PerformanceExplorer in Visual Studio by using the Menu Analyze -> Windows -> PerformanceExplorer and check if it lists any session entries. If so delete them by doing a right-click on an entry to open the ContextMenu. Then select “Remove” from the menu. You should also check the folder of your solution if it … Read more
This is actually BUG since Visual Studio 2012 that’s been open since summer 2012 with still no official MS fix. Here’s a workaround to this annoyance: From Windows explorer, go under your VS project folder Remove the following file types if present: file.vsp – (VS Performance Report) file.vsps – (VS Analyzed Reports) file.psess – (VS … Read more
The blue theme has been added back in Visual Studio 2012 Update 2, no extensions required. http://support.microsoft.com/kb/2797912
I Installed SQL Server 2012 Service pack 1 yesterday and then I started getting the problem you describe in Visual Studio 2012. Not only with database projects; I could not use the SQL Server Object Explorer, not open sql-scripts and lots of other weird database related errors. Always with the same message: “This version of … Read more
I solved this problem by clearing the Visual Studio Component Model Cache. Just delete or rename this folder: %AppData%\..\Local\Microsoft\VisualStudio\11.0\ComponentModelCache Or, for Visual Studio 2013: %AppData%\..\Local\Microsoft\VisualStudio\12.0\ComponentModelCache
When you are in the Pending Changes panel ready to check in your fix and you associate you work item with the changeset you should change “Resolve” to “Associate” (or what ever it is in Scrum). To make this the Default is more complicated. You will need to edit the Work Item Template definition for … Read more
You can use Manage NuGet packages for Solution… by: right-clicking on solution Tools > Library Package Manager > Manage NuGet packages for Solution Then you can choose in which projects install package as on screenshot below: Additionally you can add installed package to another projects in solution using the same Manage NuGet packages for Solution….
I had the same problem and wanted to change the product key to another. Unfortunate it’s not as easy as it was on VS2010. The following steps work: Remove the registry key containing the license information: HKEY_CLASSES_ROOT\Licenses\77550D6B-6352-4E77-9DA3-537419DF564B If you can’t find the key, use sysinternals ProcessMonitor to check the registry access of VS2012 to locate … Read more
EDIT: See @AnaFranco’s answer – apparently since VS2017 the file name can be configured like so: vstest.console.exe [assembly] /logger:trx;LogFileName=[filename].trx I’ll leave the old answer for posterity and pre-2017 versions. Nope, you’re not missing anything. The TRX logger doesn’t support any parameters (unlike the TFS publisher logger). The logger assembly is located in “C:\Program Files (x86)\Microsoft … Read more
I managed to ‘convert’ the solution file to change the line containing ‘# Visual Studio 2010’ to ‘# Visual Studio 2012’ in the .SLN file.