VS2003 Remote Debugging, I'll pay for a solution!

I'm having a devil of a time working with multiple vs2003 projects and
stepping them in the debugger.  If you can call me and help me do what I
need to do successfully, I'll pay $100 (paypal or a check).

My environment:
I'm running VS 2003 EE on Win XP Pro, developing asp.net apps.
I have IIS on my local machine running.
I have a W2K Server machine set up as a development web server.
Both machines are in my local active directory domain, and I have
administrative authority.
I can successfully step a project in against the local IIS instance, but not
on the remote IIS machine.

My issue:
Generally I make references to stylesheets and image files using paths from
the root of the website.  like this:

@import url(/css/Tables.css);  (a style sheet)
<img src="/Images/clientlogo.png">  (in a header custom control)

I always deploy each application to it's own website on a production W2K
Server machine.

When developing on my local machine, I have a problem with XP Pro's crippled
webserver.  Since XP Pro only allows one website, I'm stuck with virtual
directories or changing the path of the default website for each
application.  If I change the path for each project, I can't have more than
one open at a time and VS wants to call the solution file for each one
"localhost".  Harrumph.  If I use virtual directories, the paths to various
files end up different from the deployment machine, and that's a major
deployment problem.  Perhaps I'm missing something but I don't see a way to
setup my local machine so I can use pathnames relative to the web root, and
have multiple projects going at the same time.

My solution was to set up the development webserver and try to setup remote
debugging.  I've been through the help files and done what's recommended but
I still get the "Error trying to run project: Unable to start debugging on
the web server. Access is denied."

What I've done to try to make it work:
* I've run VS setup on the server and installed only the remote debugging
components.
* I've added my own domain account, the enterprise admins group (I'm in it),
and finally in desperation, "everyone" to the local debugger users group on
the server.
* I've added debugger users to the application's directory on the server.
*I've added my domain account to the local debugger user group on the local
development machine.
*I've added the web server's IP address to my trusted zones.
* I've changed the process model in the server's machine config to run in my
account as shown below.

<processModel enable="true" timeout="Infinite" idleTimeout="Infinite"
shutdownTimeout="0:00:05" requestLimit="Infinite" requestQueueLimit="5000"
restartQueueLimit="10" memoryLimit="60" webGarden="false"
cpuMask="0xffffffff" userName="mydomain\esaulsberry" password="mypwd"
logLevel="Errors" clientConnectedCheck="0:00:05"
comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate"
responseDeadlockInterval="00:03:00" maxWorkerThreads="20"
maxIoThreads="20"/>

I've also gone through the steps for ASP Remote Debugging, including the
registry entries and the dcom permissions.  It's all no go.

What does work?  I can manually attach the process and step.  That helps,
but not exactly what I'm looking for.  Of course, I just want to set a break
point, hit F5 and have it work.


If you've made this work, respond and we'll set up a call.  I'll pay cash.
(I'll also be grateful for any suggestions anyone would like to leave).

Thanks,
Elton

esaulsberry
at
ignitecommuncations
dot
com

I am not sure if IIS in XP can handle different ports for your
application, but you my be able to set each to a different port then
change vs2003 to recognize each one on a different port.

If not create a page in the root directory that redirects according to
a key called from vs2003

ES wrote:
> I'm having a devil of a time working with multiple vs2003 projects
and
> stepping them in the debugger.  If you can call me and help me do
what I
> need to do successfully, I'll pay $100 (paypal or a check).
>
> My environment:
> I'm running VS 2003 EE on Win XP Pro, developing asp.net apps.
> I have IIS on my local machine running.
> I have a W2K Server machine set up as a development web server.
> Both machines are in my local active directory domain, and I have
> administrative authority.
> I can successfully step a project in against the local IIS instance,
but not
> on the remote IIS machine.
>
> My issue:
> Generally I make references to stylesheets and image files using
paths from
> the root of the website.  like this:
>
> @import url(/css/Tables.css);  (a style sheet)
> <img src="/Images/clientlogo.png">  (in a header custom control)
>
> I always deploy each application to it's own website on a production
W2K
> Server machine.
>
> When developing on my local machine, I have a problem with XP Pro's
crippled
> webserver.  Since XP Pro only allows one website, I'm stuck with
virtual
> directories or changing the path of the default website for each
> application.  If I change the path for each project, I can't have
more than
> one open at a time and VS wants to call the solution file for each
one
> "localhost".  Harrumph.  If I use virtual directories, the paths to
various
> files end up different from the deployment machine, and that's a
major
> deployment problem.  Perhaps I'm missing something but I don't see a
way to
> setup my local machine so I can use pathnames relative to the web
root, and
> have multiple projects going at the same time.
>
> My solution was to set up the development webserver and try to setup
remote
> debugging.  I've been through the help files and done what's
recommended but
> I still get the "Error trying to run project: Unable to start
debugging on
> the web server. Access is denied."
>
> What I've done to try to make it work:
> * I've run VS setup on the server and installed only the remote
debugging
> components.
> * I've added my own domain account, the enterprise admins group (I'm
in it),
> and finally in desperation, "everyone" to the local debugger users
group on
> the server.
> * I've added debugger users to the application's directory on the
server.
> *I've added my domain account to the local debugger user group on the
local
> development machine.
> *I've added the web server's IP address to my trusted zones.
> * I've changed the process model in the server's machine config to
run in my
> account as shown below.
>
> <processModel enable="true" timeout="Infinite" idleTimeout="Infinite"

> shutdownTimeout="0:00:05" requestLimit="Infinite"
requestQueueLimit="5000"
> restartQueueLimit="10" memoryLimit="60" webGarden="false"
> cpuMask="0xffffffff" userName="mydomain\esaulsberry" password="mypwd"

> logLevel="Errors" clientConnectedCheck="0:00:05"
> comAuthenticationLevel="Connect" comImpersonationLevel="Impersonate"
> responseDeadlockInterval="00:03:00" maxWorkerThreads="20"
> maxIoThreads="20"/>
>
> I've also gone through the steps for ASP Remote Debugging, including
the
> registry entries and the dcom permissions.  It's all no go.
>
> What does work?  I can manually attach the process and step.  That
helps,
> but not exactly what I'm looking for.  Of course, I just want to set
a break
> point, hit F5 and have it work.
>
>
> If you've made this work, respond and we'll set up a call.  I'll pay
cash.
> (I'll also be grateful for any suggestions anyone would like to
leave).
>
> Thanks,
> Elton
>
> esaulsberry
> at
> ignitecommuncations
> dot
> com