When building a Windows Service I found that I needed to be running Visual Studio as Administrator and perhaps foolishly, took these steps on How to Run Visual Studio Permanently as Administrator.
That all worked fine but I now find that when trying to debug Apps that integrate with Outlook, they won't work if Outlook is already running, so I want to run Visual Studio as normal i.e. not as Administrator.
Does anyone know how to undo this troubleshooting change? Could it require a registry edit?
Many thanks to #PMF for solving this. As suggested, following the same procedure and unchecking the checkbox in step 4 works.
I have an error in my code development environment. I can't solve it and I can't work properly rightnow.
Details:
I'm working with "Visual Studio 2015 Update 1", "Windows 8.1 ( with latest updates )". I'm launching one webapi2(resource service) and two asp.net mvc applications(backend and frontend) in Visual Studio Start - debug mode. We are using IIS express not local IIS (inetmgr) because my team mates don't want to run solution in it.
Here is the start action of one project:
The problem is:
When I (start)launch the Visual Studio for debug mode; Visual Studio opens the browser but applications won't work. Sites are stay at loading mode. It's kinda stuck. I mean; Browser is still waiting a response from IISexpress to show, but there is no response there. Here is what I saw (Yükleniyor means Loading...):
If I wait too long, Browser-IIS will give this error: "HTTP Error 403.14 - Forbidden The Web server is configured to not list the contents of this directory."
And I see this message in Diagnosic Tools Window: "The thread 0x3714 has exited with code 0 (0x0). The thread 0x2780 has exited with code 0 (0x0). The thread 0x35d0 has exited with code 0 (0x0). etc etc...". There is no error message from Visual Studio. How can I solve this problem ?
Important Note:
If I restart Visual Studio, I can debug the application JUST one time!. If I click the stop and run again, the problem comes back.
Another Note: I tried to contact with Microsoft. I wrote the same problem to them. But 2 weeks pasted, they are not returned back yet.
I tried already:
Working in release mode
Open Visual Studio in Safe Mode.
Restore Visual Studio
Uninstall and reinstall Visual Studio
Uninstall and reinstall IIS Express
Uninstall only VS update 1
Tried in another 2 computers ( Solution and applications are working well. )
In my system the problem seems to be solved. I updates the following items by "Tools/Extensions and Updates ..." menu of Visual Studio 2015:
Microsoft ASP Net Web Framework And Tools (Version 5.2.40204.0).
Microsoft ASP Net Web Tools (Version 14.201.20203.0).
Web Essentials 2015.1 (Version 1.0.207).
I think the problem was solved by update N. 2, but for completeness I reported all items updated.
The issue seems similar to the one I am experiencing in an ASP.NET MVC app. SignalR v2.2.0 was the culprit in my case and the temporary easy fix that worked for me was to replace app.MapSignalR(); in my Startup class with this:
var task=Task.Run(()=>app.MapSignalR());
task.Wait(300);
if (task.IsCanceled)
{
Task.Run(() => app.MapSignalR()).Wait(300);
}
This solution was provided by JonasSyrstad on this SignalR issue thread, along with other useful info: github.com/SignalR/SignalR/issues/3414#issuecomment-75537540
Apparently, the problem is not specific to SignalR. You can find more details in Kaspars Ozols' answer on another thread:
https://stackoverflow.com/a/34227866/4491770
I had the same issue, Nb 1 from Marco fixed the problem: install Microsoft ASP Net Web Framework And Tools (Version 5.2.40204.0).
Easy workaround until this problem is fixed:
Start command prompt in elevated mode.
Execute: taskkill /f /im iisexpress.exe
Maybe this is already not important but I faced the same issue and tried to solve for 3 days.
Finally, uninstalling and re-installing the IIS Express 10 solved the issue.
I am not allowed to add a comment, as I do not have a rep of 50+ but I did want to chime in and say, I was experiencing this as well from work on Wednesday. I upgraded to VS 2015 Enterprise from VS 2015 Pro. Worked on the same solution/projects I do everyday and boom..
Run project in debug mode and symptoms:
the pages stall on load to browser
I set breakpoints in the code -- Controller and in the Razor View to see all the way up until the page is finished on the "server side".
The breakpoints are hit in normal fashion, but the response never seems to make it to the browser.
All I can say, is it seems very similar to Lost_In_Library's issue.
Attempted but persists:
/ResetUserData and /ResetSettings
Hope this helps in some way. I'd also like to point out, I have one non default use case, after resetting VS, I have to config for IIS express 64 bit, that is only non default setting I have configured.
I faced this problem also.
I think it's a BUG of VS2015 or something related.
I found a ugly solution: KILL the sub-process.
use Process Explorer from SysInternals Suite
1. Right click the node of iisexpress.exe
2. select "Kill process tree"
3. F5 works.
Simply running my Visual Studio (Update 2) in Admin mode solved it for me.
Be sure to run Visual Studio as an Administrator. I was having the same issue and that solved being able to Debug with IIS Express.
I've got the same during use MvcSiteMapProvider 4.6.22.
How to repeat:
I used VS 2015 SP3 and created ASP.NET MVC 5 Application.
Then I added via NuGet package manager MvcSiteMapProvider.MVC5 (version 4.6.22).
The manager added 4 packages:
MvcSiteMapProvider.Web (v4.6.1)
WebActivatorEx. (v2.0.1)
MvcSiteMapProvider.MVC5.Core (v4.6.22)
MvcSiteMapProvider.MVC5 (v4.6.22)
I got "IIS hanging" after start debug of this solution. But next time the solution started fine and IIS hung only after few restarts of debug.
May be you should revise your referenced assemblies in your project?
If you experience this issue with Visual Studio 2017, then you may need to ensure that your installation included the selection of the option:
ASP.NET MVC 4
I tried re-targeting my solution to .NET 4.6, 4.5 and 4.5.2 using Web platform Installer without success. This option must include a critical runtime component.
My visual studio 2013 suddenly keeps saying visual studio has stopped working.
You can`t un instal or repair. I ran it on the safe mode,Admin no result.
Formatted my whole system, installed 2013 express, 2015 community. the problem doesn`t go away.
I don`t konw what else to do?
any help?
Please Check that you have the required Frameworks needed to start it.. There might be a hardware compatibility problem.
You can try with process Explorer & Process Monitor to diagnose what is happening.
one sample video of issue diagnosis.
Whenever I try to debug a Visual Studio 2010 web project, VS hangs, and ultimately crashes. This happens if I try to start the project using F5, or through Attach to Process, before the process list even appears.
Hitting F5 in, for example, a Windows Form project works fine, but attach to process fails here too.
Any ideas on what can be causing this? Obviously attaching to the devenv.exe process won't work as I can't get the Attach to Process dialog to appear...
Oh, running W7 (x64), VS2010 SP1 (had same problems without SP1)
In Solution Explorer there is a Show All Files icon (highlighted in the photo below):
Make sure it's turned off,
When It's turned on, Visual Studio tries to index all the files in the solution and if you have a giant Solution it could take forever!
I hope this has helped someone :)
Have you recently installed Mono and/or Mono Tools for VS2010?
I found that to be the problem it my case. Not sure why, but it somehow got in the way.
Matthew
In my case hangs when executable type was not correctly set, ex. Managed v4.0 and trying to attach to Native.
My Visual Studio crashes each time I try to debug my ASP.net application.
I've been working on this application for months and only now has this issue come up. I've tried rebooting to no avail.
When I press F5, Visual Studio immediately freezes up and displays no error message. I also get the exact same behavior when I use the "Attach to Process" option to start the debugger.
The problem happens only with a particular application I'm working on. If I create a new project, I can debug that project, but as soon as I open up my original project, it's the same story all over again.
Also, I should point out that the "development server" icons appear in the System tray and do not disappear after the frozen Visual Studio 2008 is terminated.
Has anyone else encountered this?
I had the sysadmin re-install VS2k8 for me. That fixed the problem.
For some odd reason, the uninstall process took a very long time that surprised even the sysadmin who uninstalled and reinstalled it for me. I wonder if that could have anything to do with the problem.
Anyhow, the reinstall got me up and running again.