DotNetNuke

Re: (screen shots) How to quickly Debug DNN4

MNF — Tue, 17 Jan 2006 07:06:13 GMT

In my case I am using additional (not core DNN) libraries, that also can be unchecked for quick start, but should be checked back if any modification were done.

Re: (screen shots) How to quickly Debug DNN4

adefwebserver — Tue, 17 Jan 2006 02:38:53 GMT

I should have been clearer and indicated that this tip is for module development where you don't change the Core code. If you are altering the Core code then having them unchecked will not work for you :)

Re: (screen shots) How to quickly Debug DNN4

MNF — Tue, 17 Jan 2006 02:29:36 GMT

If you uncheck libraries from Configuration Manager, don't forget to check them on, if you do any modification in them. It is required to rebuild not only one library but all in dependency path between DotNetNuke Web Site and changed library. See my blog post for more details.

Re: (screen shots) How to quickly Debug DNN4

adefwebserver — Wed, 11 Jan 2006 14:14:26 GMT

If you get errors trying to debug a VS2003 application in VS2005 or debugging an application from another machine see:

http://msdn2.microsoft.com/en-us/library/0y3b8byc.aspx

Re: (screen shots) How to quickly Debug DNN4

adefwebserver — Sun, 27 Nov 2005 14:34:09 GMT

Thanks I updated the first post so it's all in one place :)

Re: (screen shots) How to quickly Debug DNN4

J7Mitch — Sun, 27 Nov 2005 05:06:35 GMT

Thanks for sharing Michael. Cutting down on the compile time when doing "run" from the IDE like that will really speed up the start of the debugger.

BTW, another way to quickly get into debug mode is to browse to your website normally through a browser, then in the IDE you can select Debug > Attach to Process, then select the aspnet_wp.exe process that the website is running under.

(screen shots) How to quickly Debug DNN4

adefwebserver — Sun, 27 Nov 2005 03:16:34 GMT

1. In Visual Studio 2005 Standard, select BUILD then "Configuration Manager"

2. Uncheck all the "Build" boxes for all the Projects except for the project that begins with "http://" and click CLOSE

3. Select "Build" then "Build Solution"

4. Go back to the "Configuration Manager" and un-select the "Build" box for the project that begins with "http://" and click CLOSE

5. You should now be able to Debug quickly.

Another way (suggested by J7Mitch) :

1. Go to "Debug" then "Attach to Process"

2. You may see more than one "aspnet_wp.exe". Hover your mouse over each one and they will identify the asp.net version (after a second or so). Select the one that is "\v2.0..." and click "Attach"

3. Set your breakpoint in VS 2005 and then browse to your page in your web browser.