How To Debug A Dump File For An Worker Process In Visual Studio 2010
Aug 23, 2010
I've run into a particularly nasty bug where an ASP.NET website attempts to make a call to a WCF service method that sends IIS into a death spiral...that ultimately brings down the associated app pool. It never gets to our log4net code that outputs unhandled exceptions.I was watching w3wp.exe processes spin up and die, so I figured I'd take a dump file on termination using ProcDump from SysInternals using the following command
I made a small app to capture frame from video using asp.net, in visual studio, it works fine. however the problem arises when i try to use any other servers, I am currently using iis 7.5, and trying to debug on server, but alas when i reach some region of code the attached w3wp.exe just get detached, the process crashs, no debug available anymore.
Unable to start debugging on the web server. The IIS worker process for the launched URL is not currently running.I'm running Windows 7 64 bit, VS 2008 sp1.When I first try to debug I get the error msg above. I wait a few minutes (presumably some service is starting) and debugging will start but no breakpoints are recognized.Some of the things I've tried:Changing the binding of my site from a static IP to "*".
Enabled windows authentication.made sure localhost = 127.0.0.1 in the hosts file.The website was built under windows xp and whatever version of IIS ships with xp. My web config has no errors that I know of but might be missing something required for iis 7 (??)
This is weird: When I try to debug ASP.NET web application, Visual Studio 2010 gives me this message "Script debugging of your application is disabled in Internet Explorer", but in my IE 7 (Internet Options --> Advanced), both "Disable Script Debugging" checkboxes are not checked.
When I am actively developing it is extremely cumbersome to write some code, fire up the debugger to test said code, wait a minute for the debugger to start, look at the page in the browser, stop the debugger, edit the code, rinse, lather, repeat. I can get around that by using CTRL-F5 and CTRL-SHIFT-B during development but I lose all the benefits of the debugger. Is there a better way to use the debugger, or something else I can do to get quick rebuilds and use of the debugger? I/we do write unit tests, but you also need to test your app in the browser so please no "you shouldn't have this problem if your unit tests were written properly"
I am having a hardtime script debugging in VS2010 and IE8. I am using .net 4 framework.When i try to make a break point in my client script in VS2010, i get the respond "This is not a valid location for a breakpoint". Then I have tried to use IE8 Developebar, but when i try starting the script debugger it throws an alert, and tell's me that it couldent attatch to the process, because there may be another debugger attatched to the process.
I am using Visual Studio 2010 and ASP.NET 4.0 to build a WebForms project that uses the new routing features in System.Web.Routing. When I build my solution and run it from within VS.NET's debugging environment only routes with RouteUrl's that include a ".aspx" extension are being properly routed to the PhysicalFile. It appears requests made to other URLs are not being "detected" by the routing engine for processing. In the case below, "Scenario1" shows a 404 and "Scenario2" works properly.
I am trying to debug a project, suddenly I'm running into an issue where enumerating any object collections results in a timeout if I try to view it.If I run the program normally I have no issues. If I try to view any collection, such as a list, I get a timeout error and the whole thing bombs out.I thought something might be going on with one of my more complex collections so I tried creating just a normal list of strings as follows...
List<string> blah = new List<string>{"fsdf","fsdg","Gt","gsersg","ser","gersgxdrsd"};
I have just the Express version of VS2010 so no option to attach to process. I am developing a custom DotNetNuke module which runs fine by itself, but has problems when running once installed as a module in DNN. Hence I need to attach to the DNN process and see what is going on. I don't have DbgCLR.exe as it looks like they stopped including that in .NET 3.5 Framework...and I don't want to risk installing .NET 2.0 framework and mess up my dev environment.
I have loaded Web Site from HDD. Now trying attach it to process WebDev.WebServer.EXE. But in Visual Studio 2010 Web Developer Express edition of VS not exist tool Attach To Process. Is it normal? if yes,
I recently upgraded from VWD 2008 Express to VWD 2010 Express. A problem has developed in that the website's graphics no longer appear in Design mode, there are "Error Creating Control" error messages that did not exist before, and also debugging errors that did not exist before. (Note: these problems did not exist when I first used VWD 2010; they may have originated with recent automatic Windows updates (I use Vista Home Premium SP2 with IIS 7)). The problem exists if I open the website either as a project file or as a website directory.
I have web project and window project.Web project reference from window project and I want to debug from web project to source code in window project. Where do I setup to look for debug source code in window project.
I copied all source code from another computer. but on another computer can debug just fine.All that different is where the source file is located. so I think it should have some config in studio that tell where the source file is.
I want to debug an ASP.Net website as it attempts to write a file to a directory.When actually deployed this file would possibly not be writeable by the worker process so an error would be thrown, this is not a problem as I just want to catch the error, inform the user and move on.Of course, if I'm debugging on my local machine then I'm an administrator and I have permission to write to the file, so I can't check that I've trapped the correct errors and I can't step through an see where it goes wrong if I haven't.
I tried to install Visual Studio Prof 2010 trail version in my system, but i got an error saying 'Please remove/uninstall Visual Studio 2010 load test controller' to proceed installation. i uninstalled my previous VS2008 software from system and i could not find anything like 'Remove/Uninstall Visual Studio 2010 load test controller' software in my Add/Remove Programs.
installing visual studio 2010 pro RC in windows Xp SP3 and getting a message prompt : invalid windows installer package contact vendorlog file says
Error Message:
[02/22/10,17:09:07] Microsoft Application Error Reporting: [2] CMsiComponent::Install() expects the setup file for Microsoft Application Error Reporting, but the file failed verification. [02/22/10,17:09:07] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InternalInstallManager() with HRESULT -2147467259. [02/22/10,17:09:08] VS70pgui: [2] DepCheck indicates Microsoft Application Error Reporting is not installed.
how I can make my VWD2010 show the window where I tick which exceptions I want the debugger to halt on throw rather than unhandled? MSDN docs imply that the menu can be customized to add it but this is NOT TRUE for my version
When i compile my vs2008 solution which is a web application in debug mode i keep getting message box displayed which says that it cannot connect "whatever.designer.cs". Can
Debug-Start Debugging/Debug-StartWithoutDebugging OR Project ASP.Net Configuration launches Dreamweaver. It started lastnight, I had both Deamweaver and VWD 2008 express open at the same time - (I was looking at JQuery in the Microsoft and Dreamweaver enviroments simultaniously). After the first tie this happened, I closed down Dreamweaver (CS3) and it opened when I tried to run my VWD project. I reinstalled VWD 2008 express, IIS and disabled Dreamweaver (renamed the exe). Dreamweaver still came up.
I have a .NET infra code running both within the IIS worker process and within a desktop client app. How can the .NET code determine whether it is running within an IIS worker process?
I know that I could check the name of the process (w3wp.exe, for instance), but I would like a more robust approach. I wish to make a side note. This is not a production need. I need this information to enable certain scenarios useful during the development and testing phase. Specifically to ease the testing of secure vs non secure configurations.