has anyone had a similar issue?
create new web application
build it, and host in IIS
try attaching to the w3wp (not F5)
Related
I am working on ASP.NET MVC project in Microsoft Visual Studio. When I run project in debug mode on my local IIS server, everything is fine. But when I stop this debug session, I got this problem.
I had to terminate manually this process. I dont know why is this hapenning. It's not ocurring everytime. Can you help me please? As a browser I am using Google Chrome. Thank you!
I have deployed a solution on a server farm and wish to be able to debug the solution's logic whilst it is running on the server farm, since the problem resides in there, Is there any way or mean by which it is possible to debug a solution (.wsp) which was deployed on a server farm, through the visual studio?
You can either click F5 in Visual Studio and it will deploy the solution and attach a debugger to the appropriate SharePoint process. This can be a little slow but it allows you to debug your code.
You can also manually attach to the SharePoint process from Visual Studio. Go to Debug-->Attach to Process-->Check show processes from all users and sessions-->Select all w3wp.exe processes-->Click attach.
I have a visual studio solution with a half dozen web application projects. I often want to attach the debugger to a process. When I do this, visual studio always wants to start up cassini or IIS express or do something to run the web applications in the solution. Is there a way I can skip that, so when attaching to a process visual studio does not try to start the web applications in the current solution?
On the project properties, there's a setting called "Development Server" -> "Always Start When Debugging." Might be worth a shot.
I have been experiencing problems with Visual Studio 2010 and debugging.
I have been getting the:
"Unable to start debugging on the web server. The IIS worker process for the launched URL is not currently running." error, but it appears VS2010 now doesn't want to function at all and is hanging.
Whenever I try to attach the debugger, it doesn't.
If I try and run the project using the custom URL and letting IIS7 server the web page, the whole IDE is now hanging.
Has anyone had problems with the debugger not attaching, running the project with the debugger causing the above error and/or Visual Studio hanging completely when running the debugger?
I can't even minimise the IDE window and it seems to flicker when I click the button.
I'm using a web application which uses a many dlls. The debugging happens by attaching the aspnet_ws process to Visual Studio. I want to explore the intellitrace feature of VS 2010 and capture the event log. But when i try to attach the process to VS 2010 i'm getting a message in the intellitrace window that this feature could not be used for an already running process. If so is there any work around to achieve this? Please let me know if anyone has an alternate.
Thanks.
IntelliTrace for Visual Studio 2010 does not support attaching to a process and collecting data.
IntelliTrace has to launch the process in question itself. You can use Visual Studio's internally hosted web server to debug locally. I'm not certain, but you may be able to do historical debugging in IIS if you load a web project via URL in Visual Studio and start debugging.