Not able to debug aspx page when called from winform

[moondaddy]

I have a .net 2.0 winforms app that calls a web service which creates
creates a GUID and caches it, then passes the GUID back to the winform.
then it opens a aspx page and passes the GUID as a parameter. this GUID is
only cached for about 10 seconds and must be still cached for the page to
load. otherwise, the page redirects to a error page. all of this forces the
page to only be called from winforms app.

I can debug from the winform to the web service and back, but the code wont
step into the aspx page. I used to do this in a vb1.1 app and it worked
great. now I'm using c#2.0 and need to step into the aspx page. can
someone please advise how I can do this. it seems that I just need to
adjust some configuration somewhere.

Thanks.

 

[Guest]

Not sure how you did this in VS2003 but: load the asp.net web app that hosts
the aspx page in a separate VS2005 instance and attach aspnet_wp.exe (if Win
XP or w3wp.exe for Win2003) process to the VS debugger (menu Deug | Attach to
Process... and make sure the type is 'Managed').

Now, run your win app and it should step in to the aspx page at the
breakpoint you set.

Hope this helps?

 

[John Saunders [MVP]]

I have a .net 2.0 winforms app that calls a web service which creates
creates a GUID and caches it, then passes the GUID back to the winform.
then it opens a aspx page and passes the GUID as a parameter. this GUID is
only cached for about 10 seconds and must be still cached for the page to
load. otherwise, the page redirects to a error page. all of this forces
the page to only be called from winforms app.

I can debug from the winform to the web service and back, but the code
wont step into the aspx page. I used to do this in a vb1.1 app and it
worked great. now I'm using c#2.0 and need to step into the aspx page.
can someone please advise how I can do this. it seems that I just need to
adjust some configuration somewhere.

Did you convert your web application into a web site when you upgraded to VS
2005?

 

[moondaddy]

Thanks for the reply,

the answer to your question is No. this is the situation.

Originaly I built an app in vb1.1 (winforms app talking to an asp.net app
which contained both the aspx page and the asmx page).

Later I installed VS2005 while retaining the install of VS2003. the vb app
continues to work fine.

Now I'm building a new - sepperate app in c#2.0 and it too is a winforms app
that needs the same functionality - call web service, cache GUID, call aspx
page and pass GUID in as param, retrieve cached GUID on server, etc...

So right now today, I can still debug the vb1.1 app from the winforms app
into the WS and back, and into the aspx page and back. But I can not step
into the aspx page in the c# 2.0 app.

 

[moondaddy]

Please disregard this thread. I figured out the problem as it was a classic
'Stupid User Error'.

When coding the URL to the aspx page I copied the url when I first ran and
tested the page on its own. this url looked something like this:

http://localhost:2100/bla bla bla...

Note the ":2100" which is how VS2005 or asp.net interpreted it.

Then I used the url for web service when it was originally created which was
something like this:

http://localhost/WebAppName/bla bla bla

it used the web app name instead of the 2100. So the web service and aspx
page really were running in different instances of the web app. I just
assumed that the urls created by VS would all work together. when converted
the 2100 to the web app name (the folder the web app lives in) all worked
fine.

Sorry to anyone who read through this thread.

 

[moondaddy]

Please disregard this thread. I figured out the problem as it was a classic
'Stupid User Error'.

When coding the URL to the aspx page I copied the url when I first ran and
tested the page on its own. this url looked something like this:

http://localhost:2100/bla bla bla...

Note the ":2100" which is how VS2005 or asp.net interpreted it.

Then I used the url for web service when it was originally created which was
something like this:

http://localhost/WebAppName/bla bla bla

it used the web app name instead of the 2100. So the web service and aspx
page really were running in different instances of the web app. I just
assumed that the urls created by VS would all work together. when converted
the 2100 to the web app name (the folder the web app lives in) all worked
fine.

Sorry to anyone who read through this thread.

Thanks for the reply,

the answer to your question is No. this is the situation.

Originaly I built an app in vb1.1 (winforms app talking to an asp.net app
which contained both the aspx page and the asmx page).

Later I installed VS2005 while retaining the install of VS2003. the vb
app continues to work fine.

Now I'm building a new - sepperate app in c#2.0 and it too is a winforms
app that needs the same functionality - call web service, cache GUID, call
aspx page and pass GUID in as param, retrieve cached GUID on server,
etc...

So right now today, I can still debug the vb1.1 app from the winforms app
into the WS and back, and into the aspx page and back. But I can not step
into the aspx page in the c# 2.0 app.