Phillip,
Not sure what you mean exactly but I follow this for all debugging:
Hit Ctrl Alt P
select machine and process
Attach
dispel window
set break point in the code
fire up browser, navigate to page
If the page has a querystring in it, I see it just fine. If you're saying
you don't have a page that is generating those query strings and you are
just testing the callee then I would mock up a quick test client page to
call your troublesome .aspx page.
Regards,
Jason S.
"Philip Townsend" <> wrote in message
news:...
> I frequently need to debug .aspx files that contain url querystrings.
> Currently, when debugging, I wait for the page to load with an
> exception, then enter the querystring and continue debugging. Does
> anybody know a way around this? Is there a way to specify the arguments
> within VS.NET? Thanks!
>
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!