Is there any way to avoid the window of development server? (Not stopping or avoiding to run the development server, just the window).
In Visual Studio 2010 (and before) it only appears when the development server was started. Now, in Visual Studio 2012 it is opened each time the project start, no matter if the development server has already started and you have closed it.
I've found that I can run projects using IIS Express. Also it will make our lives easier when we want to be able to access to the project running from other PC.
With Visual Studio 2012 it comes already installed (in fact is the default setting for projects started in it). With Visual Studio 2010 it can be installed (see post).
Related
I've been developing a Web Forms ASP.net web application in Visual Studio 2013 without any incident for some time now, but recently I attempted to upgrade to Visual Studio 2015 and now every time I launch the project I get stuck waiting for a request. This isn't a server response (like 500 or 404) it just never responds. To try and isolate this I've uninstalled every copy of Visual Studio (I had 2012, 2013 and 2015 installed), deleted the %userprofile%\DocumentsIISExpress folder, reinstalled just VS 2015, and created a completely empty web project (with just the default Web Forms boilerplate). Here is a screen shot of what I am experiencing:
I have had the same problem after installing Visual Studio 2015 Update 1. As it turns out, VS 2015 removes IIS Express 8.0, which was included with Visual Studio 2013, and installs IIS Express 10.0. For some reason, this version of IIS Express does not work for some developers.
visual studio iis express not working
iisexpress hangs when starting MVC project
Visual Studio 2015 Update 1 - No IIS Express Response While Debuging
As a workaround, I ended up uninstalling IIS Express 10.0 from the Programs and Features control panel, and re-installed IIS Express 8.0. It is available as a separate download from Microsoft.
This appears to have resolved the issues I was experiencing, however I do not know if there are features in iis express 10.0 which vs2015 relies on for debugging and app execution. In the extremely limited testing that I've done with VS 2015 and IIS Express 8.0 everything appears to be working fine YMMV.
UPDATE:
While refreshing my OS I noticed that IIS Express 10 was working properly. But when I installed IIS from the Windows Programs and Features dialog, express stopped working and behaved as described above. Others have noticed this coincidence as well.
Uninstalling IIS and reinstalling IIS Express 10, in my case, allowed me to debug my web application with IIS Express 10. As always YMMV.
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 have some web projects that run fine in the debugger in VS 2012. But when I try to run the same projects in VS 2013 i run into some problems.
First the whole Devenv.exe crashed when pressing F5.
I found an article about this problem here
It suggests set ISS Express in Visual Studio to 64 bit.
That solved the problem of the whole IDE crashing.
However, with that configuration Visual Studio tries to start "Remote Debugging". Probably because Visual Studio itself is 32 bit, so it must use some "remote" techniques to debug something 64 bit. At least that's my guess on what is happening.
Remote debugging is not succeeding either. I get "Remote Debugger has stopped Working" sometimes. Sometime at the beginning of the degugging session, and sometime at the end of the session. I found an article about this problem too. It suggest to set the web project to x86 to avoid remote debugging. But that will not work in this case. It has to run 64 bit to work with IIS in 64 bit.
Error message is
Remote Debugger has stopped Working
Then
The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted.
Anyone else seen this?
Is this a common problem in Visual Studio 2013?
EDIT: more details about the environment
I have a solution containing several projects, including two web projects.
The issue happens when I try to run any of the web projects in debugger (by pressing F5).
They are normal web projects, and I am not running anything remote.
Visual Studio itself came up with the idea of using "Remote Debugger" when I checked the "Use the 64 bit version of IIS Express for web sites and projects".
The solution was first created on a Windows 7 machine running Visual Studio 2012 and it worked well there.
When I tried to open the same solution on a new machine running Windows 8.1 and Visual Studio 2013 the problem started.
A colleague is also running the same solution on his Windows 8.1. We share the solution using a git repository.
He has both VS 2102 and VS 2013 installed. He experiences the same problems in VS 2013, so he has started to use VS 2012 for this solution.
It runs fine in VS 2012. It is the same solution and same machine as it fails in VS 2013.
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.