Tag Info

New answers tagged

1

Don't know if it's gonna help you but I was just having this problem myself. All I did was to, in Visual Studio, open Tools -> Options -> Source Control -> Plug-in Selection and change from Microsoft Git Provider to Visual Studio Team Foundation Server, click OK, then go back there and change it back to Microsoft Git Provider. The message went away after ...


0

I was able to solve the problem by uninstalling Visual Studio, removing all appdata and programdata folders that were left behind, reinstalling Visual Studio, and reinstalling the update as well as all of my extensions. It was very time-consuming, but it was the only way that I was able to get Visual Studio working again. All of my settings appeared to be ...


0

Re-run the Update 4 installation and select Repair.


0

You should disable both UAC and Firewall. I faced with this issue and solution was to disable UAC in registry. It is applicable for Window 8+ hosts, if you are running Test Controller or Test Agent on it. Refer to this article: link You can do it by the following command: reg add HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v ...


0

There is absolute no need to reinstall SSMS or VS. Just find the VS shell installer in the folder, where SSMS installer unpacks its files: 1033_ENU_LP\redist\VisualStudioShell\VSSetup and install it.


1

In an enterprise environment you always have the options of using WSUS or SCCM. I've used WSUS to update our team's VS2012 environment in the past. We haven't migrated to VS2013, so I don't know the situation for it but because the mechanism behind it is very simple I don't doubt that it will support VS2013 updates, too. Here are some articles for your ...



Top 50 recent answers are included