P
Paul W
Even though I've changed my default browser in Windows to NN, VS still
insists on firing up IE when I debug. Help please,
Paul.
insists on firing up IE when I debug. Help please,
Paul.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
C
Craig Deelsnyder
Even though I've changed my default browser in Windows to NN, VS still
insists on firing up IE when I debug. Help please,
Paul.
VS.NET is the 'issue', it has its own settings on what to use..
The easiest way is to manually attach to the process. Well, for me it is,
as I normally keep my window open, I don't want to close the browser all
the time between debugging sessions.
Goto Debug-> Processes... (or hit Ctl - Alt - P)
Under available processes select aspnet_wp.exe and Attach... (or
double-click)
click ok/close at the windows until you're back to vs.net
I used to have a macro that I ran for this, well I tried and it didn't
work perfectly for some reason....
I thought there was somewhere you could set another browser for some
reason in VS.NET as well....I'm looking, can't find it right now....
C
Craig Deelsnyder
VS.NET is the 'issue', it has its own settings on what to use..
The easiest way is to manually attach to the process. Well, for me it
is, as I normally keep my window open, I don't want to close the browser
all the time between debugging sessions.
Goto Debug-> Processes... (or hit Ctl - Alt - P)
Under available processes select aspnet_wp.exe and Attach... (or
double-click)
click ok/close at the windows until you're back to vs.net
I used to have a macro that I ran for this, well I tried and it didn't
work perfectly for some reason....
I thought there was somewhere you could set another browser for some
reason in VS.NET as well....I'm looking, can't find it right now....
OK, no luck for me. Anyway, you can use any browser, and let VS.NET
attach the aspnet_wp process, which is the only one that matters for
server debugging. In fact, if you let it launch IE as normal, then opened
up Netscape (or went to an open window of Netsacape) and tried to hit your
breakpoint, it would.
And like I said, I rarely shut my browser. I just attach/detach to the
process (detaching is as easy as hitting stop button in VS.NET)...
Also, client-side script can only be debugged using IE as the browser...
HTH
M
Mythran
Craig Deelsnyder said:OK, no luck for me. Anyway, you can use any browser, and let VS.NET
attach the aspnet_wp process, which is the only one that matters for
server debugging. In fact, if you let it launch IE as normal, then opened
up Netscape (or went to an open window of Netsacape) and tried to hit your
breakpoint, it would.
And like I said, I rarely shut my browser. I just attach/detach to the
process (detaching is as easy as hitting stop button in VS.NET)...
Also, client-side script can only be debugged using IE as the browser...
HTH
There is an option in VS.Net to Wait for an external process to connect, or
something along those lines. That way, all you have to do is hit F5 and it
will automatically start in debug mode and wait for a process to run it
(such as aspnet_wp.exe). Then, just point your browser to the web page that
you want to debug. If you wish to keep the window open, you can (that is
what I do). If you stop debugging, the window stays open and you can just
hit F5 to debug (in the IDE) then F5 to refresh the Window (in Mozilla or IE
or whatever).
HTH,
Mythran