I've been using the Team Foundation Build Notification tray application to monitor builds in TFS for about 1.5 years continuously. As of today, the tray application no longer seems to be able to connect to the TFS server. The task bar application appears to be working but does not show any build definitions. I have stopped / re-started the tray application, VS 2010, Windows 7 etc, and nothing allows it to reconnect.
I am still able to connect to, and view, the build definitions through Team Explorer in Visual Studio 2010 so I know the server is up and running. As I understand it, the tray application should connect using the Visual Studio settings! All other developers on our team can still use the tray application without any problems, so that rules out some sort of security patch or modification.
Any suggestions other than unistalling / re-installing Studio? Is there a way to just un-install and re-install the Team Foundation Server Tools Build Notification monitoring application?
Related
Every time I start VS 2017 (Enterprise) on Windows 10, it opens the Settings > Update & security > For developers screen. Why does it do this, and how can I prevent it?
Installed workloads:
.NET desktop
UWP
.NET mobile (Xamarin)
I don't recall changing anything else during installation.
I had the exact same problem when opening a Xamarin project.
(Maybe it's related to the configuration request of the Xamarin Mac Agent)
I've found that enabling the developer mode on the settings stop the
panel to popup everytime.
It shows up because of the UWP workload (along with a notification in Visual Studio that you need a developer license to develop UWP apps):
https://learn.microsoft.com/en-us/windows/uwp/get-started/enable-your-device-for-development
However, if you are writing software with Visual Studio on a computer for first time, you will need to enable Developer Mode on both the development PC, and on any devices you'll use to test your code. Opening a UWP project when Developer Mode is not enabled will either open the For developers settings page, or cause this dialog to appear in Visual Studio:
Developer mode lets you sideload apps, and also run apps from Visual Studio in debug mode.
Either switching to developer mode or modifying your Visual Studio installation to not include UWP will stop it from happening.
After opening Visual Studio 2013 successfully, I switch to the Team Explorer tab and consistently get a popup error dialog saying that, "Microsoft Visual Studio 2013 has stopped working" and "Windows is checking for a solution to the problem".
This seems to be directly related to TFS (2013 Update 4) since other tools that access TFS (like Source Control Explorer > Workspaces...) also cause the crash.
Edit: I have already tried a VS 2013 Repair. This took all morning with no different results.
This is frustrating because I cannot use TFS outside of the command-line tools. Any help would be greatly appreciated. Thank you.
Credit to Tuğrul Emre Atalay for the post: Visual Studio Crashing When Checking In.
His issue was checking in changes and having Visual Studio crash. In my case, just using the TFS tools was consistently causing a crash.
The fix for me was to only clear out the local cache and not both the server and local caches.
Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache.
I cleared this folder and I was able to use all of the TFS tools without any further issues.
I then realized that this happened since migrating to a new user name. I had copied many of my settings over from my old account folder and it must have corrupted the cache area.
I had the same issue with Visual Studio 2015 Enterprises. When i open it, VS wasn't able to connect to TFS and it crashed when i clicked on "manage connections"
The issue was not about the cache (I cleared the cache, made a repair of VS and nothing changed) but about the fact that we are currently migrating our projects from perforce to Git with Team Foundation Server.
When Visual Studio starts, it seems VS is trying to connect to TFS with linked Git repositories, but since the plugin currently used is perforce, it causes an exception somehow.
The solution is to set your source control plugin to Microsoft Git Provider (or Visual Studio Team Foundation Server if you are using it)
Here's two screen shots I took. Right after I selected the Microsoft Git Provider, the Team Explorer tab automatically refreshed and I am now able to connect to my projects.
Go to Tools -> Extensions and Updates Look for Github Extension for Visual Studio and Uninstall it
Never Mind as you can still work with Github
Now Restart Visual Studio.
Enjoy working on Team Explorer.
I just added a third monitor to my system (NEC E222W) which my NVidia GeForce 9500 GT card is able to rotate such that I get 1050x1680 resolution. However, when using this mode Visual Studio 2010 SP1 (10.0.40219.1 SP1Rel) consistently locks up (grabbing 50% of the CPU) until I kill it whenever I interact with TFS. I can work in VS 2010 until I try to do anything with TFS.
I can open up Visual Studio without issues on my other two monitors and check stuff out, etc., but the minute I move the application to my 1050x1680 monitor and start the TFS dialog, the application hangs.
Anyone have this issue? I'm pretty current on the NVidia driver (191.07) and Windows XP SP 3 is current with Microsoft Update. I'm running under a non-administrator account.
Internet has not been helpful. The only thing I found was this:
http://social.msdn.microsoft.com/Forums/en/vseditor/thread/ce9134aa-b444-49e8-99f2-01b67404156a
This: Visual Studio 2010 Freezes when using TFS is unrelated.
I am able to fire up VS 2010 on the 1050x1680 monitor, work, then shift the existing instance over to another monitor to interface with TFS (check in/out) and then shift the application back to the 1050x1680 monitor successfully. I strongly suspect something is broken with the TFS checkout dialog window.
I have about four web projects that I am hosting in IIS Express. Whenever I do a build in Visual Studio 2010, the build will be blocked until I manually kill IIS Express. The build then completes. A new instance of IIS Express is created that works as expected.
I tried to do a prebuild event to kill IIS Express with taskkill, but the lock up seems to happen before the prebuild event is executed :/
If I stop the hosted sites, Visual Studio 2010 will also build as normal.
From research, one possibility is IIS Express is trying to display a dialog that Visual Studio 2010 is waiting for the user to interact with, but doesn't actually display the dialog.
Has anyone else had an issue with IIS Express and Visual Studio 2010 locking up on building? Or some insight on how to debug this issue?
If i remember correct the last service pack for vs 2010 corrected that error (at least on my maschine).
Sounds like visual studio is trying to do something on port 80, which IIS is blocking ( thats the default listener port for it ).
A simple google search of port 80 visual studio brings up several promising hits ( how to configure it, and hey! 2nd one even has a fix for a similar problem. )
This happens to me constantly, but then again I'm using WinXP / VS2010 / IIS Express 7.5. I suspect the WinXP part is the culprit, perhaps a bug for this particular scenario? At any rate, VS2010 wants to rebuild one of my web apps, but appears to wait indefinitely on some files in the Temporary ASP.net directory for the web app, until I stop IIS Express.
Does anyone know how you can install/run the TFS Team Explorer in stand alone mode when Visual Studio 2008 is installed on the same machine?
Additional Information: I should have been a little more clear in my question. I'm trying to access the Work Items.
The TFS Team Explorer will always integrate with a version of Visual Studio (apart from Express) if it is installed and there is no way of running it stand-alone.
If you install the TFS 2008 Power Tools, then you can have it so that you get Windows Explorer integration for TFS which many people enjoy. You might also want to look at Team System Web Access to provide a mechanism for accessing TFS from just a web browser (but obviously doesn't include full version control capabilities)
Finally, the company I work for has a completely standalone TFS client called Teamprise Explorer that is implemented in Java, however this is a commercial product.
Hope that helps,
Martin.
The answer is that there really isn't a standalone version. When you install VS Team Explorer on a machine without Visual Studio, the installer will install a Visual Studio shell. Then, when you run Team Explorer in standalone mode, you are actually running a Visual Studio shell.
Martin had a good point about Team System Web Access, which probably would do the job nicely. Plus it has the added benefit that it allows non Visual Studio users access to work items. But, it was decided that it was too much trouble to get permission to install it here (working for the US Army can have its issues).
My solution for now is to run another instance of Visual Studio and access the Team Explorer tools from there.