Solved

ASP.NET Remote Debugging (client using IIS5 XP and server using IIS6 2K3)

Posted on 2003-11-03
6
643 Views
Last Modified: 2007-12-19
Hi,

I have a problem when using VS.NET 2002 from my client machine using XP Pro IIS5.  I can create a web application on the server running 2K3 IIS6, but it cannot configure the root directory.  It tells me it could be because of the client/server running different versions of IIS.  I also have FrontPage Extensions 2002 installed on both, though I just use the file share web access method.  Is there some settings on the server side that I can set to allow this to work properly?

Thanks!
0
Comment
Question by:lconnell
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
6 Comments
 
LVL 5

Expert Comment

by:harwantgrewal
ID: 9671268
you want to debug your appliction on the client write..? for that make a user which belong to the group vs developers I guess this will help you debuging you application at client side

Harry
0
 
LVL 9

Expert Comment

by:msdixon
ID: 9674695
did you install the .Net server components on the server? it automatically sets up debuggin for you.
0
 

Author Comment

by:lconnell
ID: 9679504
I am trying to create and debug from a client to the server.  Meaning the ASPX project is on the server, I want to debug from the client.

.NET server components?  I installed VS.NET 2002 which installs the deubbing components.  By doing this though, when I try create an ASPX project locally or remotely, it tells me it can't connect to the web server.  So to fix this I have to uninstall IIS, then reinstall it using the ASP.NET options in W2K3 Server.  

I am not sure what else to do.
0
 

Author Comment

by:lconnell
ID: 10157090
Figured it out.

All you have to do is make sure you have an account on the server with privileges in the debug group i also made me an administrator also.  Now I did do this before posting here, so what the problem ended up to be was my isp provider doesn't allow port 80 open so i had to change IIS to port 81 thus breaking my debug connection from my client, because its looking to connect on port 80.  :)
0
 
LVL 2

Accepted Solution

by:
Lunchy earned 0 total points
ID: 10186084
PAQed, with points refunded (500)

Lunchy
Friendly Neighbourhood Community Support Admin
0

Featured Post

Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A basic question.. “What is the Garbage Collector?” The usual answer given back: “Garbage collector is a background thread run by the CLR for freeing up the memory space used by the objects which are no longer used by the program.” I wondered …
Welcome my friends to the second instalment and follow-up to our Minify and Concatenate Your Scripts and Stylesheets (http://www.experts-exchange.com/Programming/Languages/.NET/ASP.NET/A_4334-Minify-and-Concatenate-Your-Scripts-and-Stylesheets.html)…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have. In this…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question