D
dethonlegs
Hi,
I have a small vb.net app that runs as a cgi under IIS6. When compiled
under VS.NET 2003 (framework 1.1) I can launch the dubugger from IIS by
adding the line "System.Diagnostics.Debugger.Launch" in my code.
However under VS.NET 2005 (framework 2.0) the same application ignores
any attempt to launch the debugger when run from IIS. In addition,
there are many security permission issues that are causing me greif
that were not an issue under VS.NET 2003.
My questions are:
1) How do I launch the VS2005 debugger from my vb.net cgi under IIS6?
2) How do I get resolve the security issues when trying to access the
System.Environment namespace.
NOTE: I have VS2003 and VS2005 installed on the same machine. The IIS6
server is also on the same PC.
Thanks
Joe
I have a small vb.net app that runs as a cgi under IIS6. When compiled
under VS.NET 2003 (framework 1.1) I can launch the dubugger from IIS by
adding the line "System.Diagnostics.Debugger.Launch" in my code.
However under VS.NET 2005 (framework 2.0) the same application ignores
any attempt to launch the debugger when run from IIS. In addition,
there are many security permission issues that are causing me greif
that were not an issue under VS.NET 2003.
My questions are:
1) How do I launch the VS2005 debugger from my vb.net cgi under IIS6?
2) How do I get resolve the security issues when trying to access the
System.Environment namespace.
NOTE: I have VS2003 and VS2005 installed on the same machine. The IIS6
server is also on the same PC.
Thanks
Joe