Whenever i try to debug new dot net core application, dotnet.exe crashes immediately and not able to debug my application. I am getting following detail in output window:
The program '[4220] dotnet.exe' has exited with code -2147450750 (0x80008082).
The program '[3468] iisexpress.exe' has exited with code 0 (0x0).
Error code 0x80008082 is for CoreHostLibLoadFailure based on what i have searched on internet but not able to found something which provides detail about how to solve this problem. I need help to solve this problem.
Not sure whether solution will work for everyone but i am able to resolve issue by installing update KB2533623. I have windows 7 SP1 32 bit installed my PC.
Related
I have a Windows 10 laptop and am running Visual Studio 2017 (15.3.3). When I try to debug my Angular 4 app hosted in an ASP.NET page I get an error stating Cannot debug some of the code in the process chrome.exe and that the WebKit code succeeded and Script code failed (0x80040154). See error details below:
Please help.
I ended up fixing it by uninstalling VS2017, deleting the C:\ProgramData\Microsoft\VisualStudio directory and then reinstalling VS2017. This is not a great solution but it was the only one I found that worked.
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.
If I try to debug an application in VS2015, I Always get the error
"csc.exe" exited with code -1.
If I try another project (winforms/console application/...) I always get the same error. I previously had VS2008 installed for developing apps for WIN CE-devices, and I thought that might be the reason, but I already uninstalled VS2008, and reinstalled VS2015 (multiple times).
I have no other ideas what to do, did anyone had the same problem earlier?
Since this morning I keep getting this same message "Visual Studio Remote Debugging Monitor has stopped working" and no matter how many times I restart VS or Windows, that doesn't help. Unfortunately I must use x64 debugging due to third party components. I had no significant changes on the system. From last time everything worked fine.
I've seen this question
VS2008: Unable to start debugging, Remote Debugging Monitor has been closed
and it helped me to understand what is happening but doesn't help me fix the problem...
I am debugging x64 app in local and remote debugger snaps always at the same point of the app start up. The other application still works fine.
Does anyone have some solution for this?
I had a similar debugger issue where details showed that "Fault Module Name" is SYMSRV.dll. So I've fixed that by ticking off "Microsoft Symbol Servers" (Tools->Options->Debugging->Symbols) and cleaning symbols cache.
Sorry, I'm not good at English. I had the same problem. It only happened on my workstation win7 VS2010+SP1. I found that it happened when the program trying to load the assembly "EnterpriseLibrary.ExceptionHandling.Logging.Configuration.Design.dll". Strangely, this assembly references itself! so when the program execution is passing through the statement Assembly.Load("EnterpriseLibrary.ExceptionHandling.Logging.Configuration.Design") in debug mode, the msvsmon.exe crashes with this error message: "visual studio remote debugging monitor has stopped working".
Go to “Start > Run”. Type the following path and hit Enter
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
I have a VB.Net windows forms application that has been around for a very long time. I am working the project in Visual Studio 2010 Premium, on my Windows 7 x64 workstation. Everything has been going along fine till a couple days ago. No every time I build this project Visual Studio 2010 crashes.
The only thing i have to go on is this from another Visual Studio 2010 instance that attached the debugger to the dieing process.
...
The thread 'Win32 Thread' (0x177c) has exited with code -2147023895 (0x800703e9).
The thread 'Win32 Thread' (0xc44) has exited with code -2147023895 (0x800703e9).
The program '[4224] devenv.exe: Native' has exited with code -2147023895 (0x800703e9).
No one else on my team has this issue, and I don't have problems with any other projects.
This is .Net 4.0.
Any thoughts or suggestions are much appreciated,
Beezler
It might be wise to start VS with the /safemode parameter.
I also had this problem and I solved it by uninstalling the Achievements extension.
Do you have any modifications whatsoever to the solution/projects/code that are different from the team members not experiencing the crash? Have you tried getting a fresh-cut of the source to a different directory and trying to build that?
Another thing to look at would be to disable any add-ins/extensions you might have installed.
I had the same problem but with C++ projects. They ran fine for a while, then all of a sudden just started crashing on every build. This fixed it for me:
To fix: click start, type "cmd" into the search box, right click "cmd.exe" in the search results, select "run as admin", then run this command: regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"
Reference: http://connect.microsoft.com/VisualStudio/feedback/details/533194/crash-while-compile-an-extremely-simple-c-project
If that doesn't work, the plugin AnkHSVN is known to cause the same problem. http://blogs.msdn.com/b/visualstudio/archive/2010/05/11/if-you-are-seeing-intermittent-crashes-with-vs-2010.aspx
This is weird and i've also faced a similar issue like that. First i add a watch to a class. and when i try to drill to details of class collection, process terminates and debugging stops.
I've figured out that, it is giving stackoverflow error code. Base of the exception was just because of infinite loop.
So i re-checked all collections twice to find the property that causes a loop. like
int a {get {return MethodThatAlsoReturnsA();}
hope it helps s.o.