Groups | Blog | Home
all groups > visual studio .net debugging > january 2004 >

visual studio .net debugging : Can only attach manually.....


jdn
1/26/2004 10:56:08 AM
I'm at a client site, and am having an issue that may or may not be resolvable

Different servers involved, depending on stage of the process. One is in the same domain, the other is in another domain

We connect to the project on the server, and then work offline to debug (so we debug on our local workstations by setting Project\Web Project\Work offline in the IDE). When I F5/Debug when working on the project that is located on the server in the same domain, every thing is fine

Issue comes up with the server in the other domain. There is NOT a two-way trust between the domain my local workstation sits in, and the remote server. Thus, whenever I open the project, it gives me a "Project is on an untrusted web server" warning message, but I can still open it, add files, etc. (I have sync'd my username\password in both domains also). I can also tell the IDE to work offline

However, when I try to F5/Debug, it tells me "This project is not configured to be debugged", and when I look at my local web server's logfiles, I see a 403 return code on the page set as startup

However (again), if I do a Ctrl+F5/Start without debugging, and then manually attach to the process, it works just fine

Is there a workaround for this? If I can guess what is happening, when I do F5, it is trying to launch the debugger as "RemoteDomain\Username", and since the RemoteDomain is not trusted, it gives the misleading "project is not configured to be debugged" (the project is configured to be debugged, the security settings within the IIS MMC console are the same as other offline projects, and the directory security settings on my VSWebCache subfolders are identical). But, when I attach manually, it is attaching as "LocalDomain\Username"

Any ideas

TIA

timhuang NO[at]SPAM online.microsoft.com
1/27/2004 6:32:31 AM
Hello,

Thanks for your post. As I understand, the problem you are facing is that
you cannot debug an ASP .NET web application reside on a server in another
domain. Please correct me if there is any misunderstanding.

I suggest that you can create a new User account in RemoteDomain which has
the same UserName and Password with the one in your LocalDomain, assign it
enough priviledge on the Web server, and then check whether or not the
problem still exists.

Otherwise, I am afraid that you may have to configure trusting
relationships between two domains.

I look forward to your result.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
jdn
1/27/2004 12:41:51 PM
[quoted text, click to view]

I've done all that, but that isn't the problem.

I already know I cannot debug remotely because of the domain situation
(and the firewall blocks RPC).

What I don't understand is why I can't debug the project when in "work
offline" mode (which is thus running on my machine) by hitting F5. I
can only debug if I launch the web application and then attach manually
to the asp.net process.

Why does it tell me "the project is not configured to be debugged" when
it is so configured (project properties are confirmed)?

Habib Heydarian [MSFT]
1/28/2004 2:44:01 AM
Are you getting this error even _after_ you set the IDE to offline mode, so
you're not even trying to connect to the untrusted domain?

HabibH.

[quoted text, click to view]

Wei Ci Zhou
1/28/2004 1:01:27 PM
Hi:
I think it is caused by the setting in the configuration
I think you can get useful information from this article.
http://support.microsoft.com/default.aspx?scid=kb;en-us;306156

Best Wishes
Wei Ci Zhou

AddThis Social Bookmark Button