CODEWITHSUNDEEP
visual-studio-2008debuggingiisasp-classic
opensas
opensas

Reputation: 63605

I can no longer debug classic asp code with visual studio 2008

I've finally found a way to debug classic asp code in visual studio 2008 ... but...

has anybody been able to debug asp classic code with visual studio 2005 or later?

... but ...

it only lasted a few days...

I'm following these steps

http://www.codeproject.com/KB/debug/DebugVBScriptVS2008.aspx

http://codepagoda.com/2009/04/30/debugging-classic-asp-with-visual-studio-2008-sp1-and-35-framework/

but now, when I do "attach process" I can no longer see the "Script, x86" process anymore...

so I can not debug classic asp code...

I tried restarting the machine, creating a new project, startgin from scrath, the only thing I haven't tried so far is to reinstall IIS...

any idea???

PLEASE HELP!!!!

edit: some info about my environment

Windows XP 2002 SP 3, IIS 5.1, Visual Studio 2008 9.0.30729.1 SP

Upvotes: 3

Views: 3041

Answers (3)

Vinod Srivastav
Vinod Srivastav

Reputation: 4253

The following steps might help you:

  1. Host the site is IIS and make sure it's running
  2. Change the Application Configuration to enable debugging enter image description here
  3. Then Attach the debugger to w3wp (IIS worker process) enter image description here

Upvotes: 0

walash
walash

Reputation: 1

I had the same problem. I fixed it out installing Service Pack 1 for my Visual Studio 2008. And now I attach to "inetinfo.exe" process instead of "dllhost.exe".

Upvotes: 0

AnthonyWJones
AnthonyWJones

Reputation: 189535

The most likely reason for this is because the process hasn't spun up yet. You need to hit an ASP page first before IIS spins up the DLLHOST.exe in which it runs an application if you have that application set to have high isolation (recommended for debugging purposes).

Hence debugging bia attachment requires the you use the browser to ping an ASP page in your site first, then open the Attach to process list.

Upvotes: 2

Related Questions