Re: How to debug using a private address?

Ok, DEBUG is listed for all asp/asp.net extentions.

So I re-assigned the default web site to the application folder. I
started debugging. First, it said the site was configured for .Net
1.1. It set it fo 2.0 for me. Then it said debugging wasn't enabled
in web.config. It did that. Then, miracle-o-miracles, it actually
loaded the site in a browser and stopped at the breakpoint I set.
That worked!

So on the server, I opened the original web I was working on by
specifying it through IIS (not by entering a URL). I get the same
error.

On my firewall, from Unstrust to DMZ, I've opened TCP port 135 and UDP
ports 4500 and 500. This made no difference.

So although I got localhost debugging to work, debugging using any
other method (remote, by URL, by IIS) doesn't work still and I can't
see it being a firewall issue. The sites in question have all their
asp.net settings set to 2.0 but the "Web Sites" branch says 1.1 and is
greyed. I don't know if this is an issue or not but I can't change it
for some reason.

Thanks!


On Mon, 21 Aug 2006 17:16:05 +0100, "Tim_Mac"
<tim.mackey@xxxxxxxxxxxxxxxx> wrote:

hi Fred,
sorry i should have said to look in the Home Directory tab on the web site
properties, and then hit the configuration button. this is where you see
the mappings for all the file types supported.
e.g. ASAX > aspnet_ISAPI.dll > HEAD,POST,GET,DEBUG
if DEBUG is not listed for the file types you are using, a debug request
will fail.

i use host headers too on my server. if the default web site is not being
used, you can configure it with the same home directory as your sub-domain,
this web site is set to run off localhost by default. then you could use
the default web site (off localhost) to debug.

does that make sense?
tim


"Fred Flintstone" <idontthinkso@xxxxxxxxxx> wrote in message
news:gpjje2h88p3b8vsdogmc1todua3p6bqfge@xxxxxxxxxx
"in the IIS properties for the web site, is the DEBUG verb allowed for
the file types you are trying to debug?"

I'm not sure what you mean about DEBUG verbs. I don't see this or
anything relating to file types anywhere in the website configuration.

" as an alternative testing option, could you run the web site off
127.0.0.1 and try debugging via localhost?"

The web server relies on host header names and contains many domains
and subdomains on one IP address. How can I debug a subdomain on this
server locally without a proper DNS name?

Thanks for the replies! :)


On Mon, 21 Aug 2006 16:00:58 +0100, "Tim_Mac"
<tim.mackey@xxxxxxxxxxxxxxxx> wrote:

hi Fred,
in the IIS properties for the web site, is the DEBUG verb allowed for the
file types you are trying to debug?
also, as an alternative testing option, could you run the web site off
127.0.0.1 and try debugging via localhost?

seems strange to get that error because VS 2005 is very good at debugging
compared to VS 2003 (for config issues and firewalls etc).

tim.

--------------------------
blog: http://tim.mackey.ie

"Fred Flintstone" <idontthinkso@xxxxxxxxxx> wrote in message
news:ksgje290glgdr9ucmmas81jamvphpfii7o@xxxxxxxxxx
No, you're right! If I try to debug right on the server I get the
same error message. The remote debugger monitor window is right there
and nothing happens within it. I opened it using the "Local IIS"
option instead of entering a public URL. That should eliminate the
firewall issue I think. This is getting messy.

Here's something else wierd:

Building directory
'/test/_vti_bin/_vti_adm/aspnet_client/system_web/1_1_4322/'.
Building directory '/test/_vti_bin/_vti_adm/help/1033/publish/'.
Building directory '/test/'.

I have no idea why it's building 1.1. My app and the website are
configured for 2.0.



On Mon, 21 Aug 2006 15:12:48 +0100, "Tim_Mac"
<tim.mackey@xxxxxxxxxxxxxxxx> wrote:

hi Fred,
if VS is installed on the server, can you remote desktop into the server
and
debug locally? apologies if this is only suggesting the obvious.

tim






.