|
.net
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
VS2005 Enable ASP.NET Debugging in Class Library AppIn VS2003 I had a class library project that I started via a URL and I had
ASP.NET debugging enabled to allow me to debug the web pages code behind in my project. I have moved the app to VS2005 and I no longer have that option (Enable ASP.NET debugging checkbox on the project properties Debug Tab). I can still debug the app by attaching to the aspnet_wp.exe process. However, is there another way to do it - has this option been moved elsewhere? For an ASP.NET 2.0 website you will find that setting in the web.config.
http://msdn2.microsoft.com/en-us/library/s10awwz0.aspx Brennan Stehling http://brennan.offwhite.net/blog/ Show quote "Peter Sutcliffe" <PeterSutcli***@discussions.microsoft.com> wrote in message news:631ED862-04B9-4106-9CA4-D28A00E5B109@microsoft.com... > In VS2003 I had a class library project that I started via a URL and I had > ASP.NET debugging enabled to allow me to debug the web pages code behind > in > my project. I have moved the app to VS2005 and I no longer have that > option > (Enable ASP.NET debugging checkbox on the project properties Debug Tab). > I > can still debug the app by attaching to the aspnet_wp.exe process. > However, > is there another way to do it - has this option been moved elsewhere? The compilation debug setting in the app's Web.Config is already set to
"true". This project is a class library started from a URL, not a web project. The reason that it is a class library, rather than a web project is rather involved and not particularly relevant, but basically comes down to the way VS interacts with VSS for web projects, especially when you have different, branched versions. Anyway back to the problem. In VS2003, one used to have to check 'Enable ASP.NET debugging' on the Project properties, before debugqing was effective, even when the code was compiled with debug set to true. This setting ('Enable ASP.NET debugging' ) does not exist in VS2005. I was hoping there was a subsitute. So it looks as though I will have to attach to the aspnet_wp.exe process if I want to debug. Show quote "msnews" wrote: > For an ASP.NET 2.0 website you will find that setting in the web.config. > > http://msdn2.microsoft.com/en-us/library/s10awwz0.aspx > > Brennan Stehling > http://brennan.offwhite.net/blog/ > > "Peter Sutcliffe" <PeterSutcli***@discussions.microsoft.com> wrote in > message news:631ED862-04B9-4106-9CA4-D28A00E5B109@microsoft.com... > > In VS2003 I had a class library project that I started via a URL and I had > > ASP.NET debugging enabled to allow me to debug the web pages code behind > > in > > my project. I have moved the app to VS2005 and I no longer have that > > option > > (Enable ASP.NET debugging checkbox on the project properties Debug Tab). > > I > > can still debug the app by attaching to the aspnet_wp.exe process. > > However, > > is there another way to do it - has this option been moved elsewhere? > > > Hi, Peter.
Have you read this MSDN Library page ? "How to: Debug from a DLL Project" http://msdn2.microsoft.com/en-us/library/605a12zt.aspx Juan T. Llibre, asp.net MVP aspnetfaq.com : http://www.aspnetfaq.com/ asp.net faq : http://asp.net.do/faq/ foros de asp.net, en español : http://asp.net.do/foros/ =================================== Show quote "Peter Sutcliffe" <PeterSutcli***@discussions.microsoft.com> wrote in message news:BBE786A2-6CD7-47D0-B005-D1AC41166B3D@microsoft.com... > The compilation debug setting in the app's Web.Config is already set to > "true". This project is a class library started from a URL, not a web > project. The reason that it is a class library, rather than a web project is > rather involved and not particularly relevant, but basically comes down to > the way VS interacts with VSS for web projects, especially when you have > different, branched versions. Anyway back to the problem. In VS2003, one > used to have to check 'Enable ASP.NET debugging' on the Project properties, > before debugqing was effective, even when the code was compiled with debug > set to true. This setting ('Enable ASP.NET debugging' ) does not exist in > VS2005. I was hoping there was a subsitute. So it looks as though I will > have to attach to the aspnet_wp.exe process if I want to debug. > > "msnews" wrote: > >> For an ASP.NET 2.0 website you will find that setting in the web.config. >> >> http://msdn2.microsoft.com/en-us/library/s10awwz0.aspx >> >> Brennan Stehling >> http://brennan.offwhite.net/blog/ >> >> "Peter Sutcliffe" <PeterSutcli***@discussions.microsoft.com> wrote in >> message news:631ED862-04B9-4106-9CA4-D28A00E5B109@microsoft.com... >> > In VS2003 I had a class library project that I started via a URL and I had >> > ASP.NET debugging enabled to allow me to debug the web pages code behind >> > in >> > my project. I have moved the app to VS2005 and I no longer have that >> > option >> > (Enable ASP.NET debugging checkbox on the project properties Debug Tab). >> > I >> > can still debug the app by attaching to the aspnet_wp.exe process. >> > However, >> > is there another way to do it - has this option been moved elsewhere? >> >> >> Thank you, but I already know how to debug a DLL Project, by starting from a
URL. The method for VS2003 works but the same is not true for VS2005. You can start the application, but it will not break at any breakpoints you set in your code until you attach the debugger to the aspnet_wp process. This was not required in VS2003. Show quote "Juan T. Llibre" wrote: > Hi, Peter. > > Have you read this MSDN Library page ? > > "How to: Debug from a DLL Project" > http://msdn2.microsoft.com/en-us/library/605a12zt.aspx > > > > Juan T. Llibre, asp.net MVP > aspnetfaq.com : http://www.aspnetfaq.com/ > asp.net faq : http://asp.net.do/faq/ > foros de asp.net, en español : http://asp.net.do/foros/ > =================================== > "Peter Sutcliffe" <PeterSutcli***@discussions.microsoft.com> wrote in message > news:BBE786A2-6CD7-47D0-B005-D1AC41166B3D@microsoft.com... > > The compilation debug setting in the app's Web.Config is already set to > > "true". This project is a class library started from a URL, not a web > > project. The reason that it is a class library, rather than a web project is > > rather involved and not particularly relevant, but basically comes down to > > the way VS interacts with VSS for web projects, especially when you have > > different, branched versions. Anyway back to the problem. In VS2003, one > > used to have to check 'Enable ASP.NET debugging' on the Project properties, > > before debugqing was effective, even when the code was compiled with debug > > set to true. This setting ('Enable ASP.NET debugging' ) does not exist in > > VS2005. I was hoping there was a subsitute. So it looks as though I will > > have to attach to the aspnet_wp.exe process if I want to debug. > > > > "msnews" wrote: > > > >> For an ASP.NET 2.0 website you will find that setting in the web.config. > >> > >> http://msdn2.microsoft.com/en-us/library/s10awwz0.aspx > >> > >> Brennan Stehling > >> http://brennan.offwhite.net/blog/ > >> > >> "Peter Sutcliffe" <PeterSutcli***@discussions.microsoft.com> wrote in > >> message news:631ED862-04B9-4106-9CA4-D28A00E5B109@microsoft.com... > >> > In VS2003 I had a class library project that I started via a URL and I had > >> > ASP.NET debugging enabled to allow me to debug the web pages code behind > >> > in > >> > my project. I have moved the app to VS2005 and I no longer have that > >> > option > >> > (Enable ASP.NET debugging checkbox on the project properties Debug Tab). > >> > I > >> > can still debug the app by attaching to the aspnet_wp.exe process. > >> > However, > >> > is there another way to do it - has this option been moved elsewhere? > >> > >> > >> > > >  |
|||||||||||||||||||||||
Other interesting topics