Visual Studio Development Bookmark and Share   
 index > Visual Studio Debugger > invalid pointer for C:\Program Files\Common Files\Microsoft Shared\DevServer\9.0\webdev.webserver.exe
 

invalid pointer for C:\Program Files\Common Files\Microsoft Shared\DevServer\9.0\webdev.webserver.exe

I have a workstation that is running VS2008 Team Developer that suddenly returns an error concerning a
Invalid Pointer webdev.webserver.exe file.    The file is in the correct folder, however this error occuring
everytime the individual using the VS2008 attempts to run debugger.

Thanks
CFosh  Wednesday, October 07, 2009 9:18 PM
Hi CFosh,

Yes, it not so convenient compared to pressing F5 to start debugging, I'm sorry. However, on some scenarios, for example, when we debug a dll which is reference to our Web/WinForm/Console whatever project, we need to attach our debugger to the executable program. That's because a pure dll could not generate an exe for our debugger to attach to.

Another workaround is to Use Local IIS Web server which could be found under Project Properties -> Web tab -> Servers section. Please check this radio button and try to launch the debugger again.

Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework!
Roahn Luo  Friday, October 09, 2009 3:46 AM
Hello CFosh,

Did we check the Visual Studio Development Server option? (which is under properties -> Web tab). If we did not select this, Visual studio will not attach to the Webdev.WebServer.exe process.

Besides, how about the issue if we run our project without debugging (Ctrl + F5) and then attach Visual Studio Debugger to the Webdev.WebServer.exe process?
Please also try to run Visual Studio in Safe mode to avoid any third part Add-in(s) which may interfere with our program.

Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework!
Roahn Luo  Thursday, October 08, 2009 7:16 AM
Thanks for the reply, your suggestion on Manually attaching to Debugger did work.  However I am left wondering, why the developer is needing to manually attached to the process each time, they want to debug?
CFosh  Thursday, October 08, 2009 4:03 PM
Hi CFosh,

Yes, it not so convenient compared to pressing F5 to start debugging, I'm sorry. However, on some scenarios, for example, when we debug a dll which is reference to our Web/WinForm/Console whatever project, we need to attach our debugger to the executable program. That's because a pure dll could not generate an exe for our debugger to attach to.

Another workaround is to Use Local IIS Web server which could be found under Project Properties -> Web tab -> Servers section. Please check this radio button and try to launch the debugger again.

Best regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback, please tell us.
Welcome to the All-In-One Code Framework!
Roahn Luo  Friday, October 09, 2009 3:46 AM

You can use google to search for other answers

Custom Search

More Threads

• Debugging Custom Component Property Editor
• Get the details of running objects in heap
• Insanely slow loading time with loading symbols for ntdll.dll
• Debugging CLR Stored Procedure
• Where is my Autos Debug window???
• Visual Studio 2008 "View in Browser" hangs ide ?
• VS 2005 crashed trying to attach to process
• My software only runs with Visual Studio, cannot run alone why?
• JIT Debugger
• Unable to start debugging....