(screen shots) How to quickly Debug DNN4

Last post 01-17-2006 2:06 AM by MNF. 6 replies.

Sort Posts:

  • (screen shots) How to quickly Debug DNN4

    11-26-2005, 10:16 PM
    • Contributor
      5,869 point Contributor
    • adefwebserver
    • Member since 06-07-2003, 12:50 PM
    • Los Angeles, CA
    • Posts 1,186

    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.

  • Re: (screen shots) How to quickly Debug DNN4

    11-27-2005, 12:06 AM
    • Star
      13,145 point Star
    • J7Mitch
    • Member since 10-19-2002, 1:23 PM
    • Posts 2,632
    • TrustedFriends-MVPs
    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.
    John M.

    DotNetNuke Module for Performance
  • Re: (screen shots) How to quickly Debug DNN4

    11-27-2005, 9:34 AM
    • Contributor
      5,869 point Contributor
    • adefwebserver
    • Member since 06-07-2003, 12:50 PM
    • Los Angeles, CA
    • Posts 1,186
    Thanks I updated the first post so it's all in one place :)
  • Re: (screen shots) How to quickly Debug DNN4

    01-11-2006, 9:14 AM
    • Contributor
      5,869 point Contributor
    • adefwebserver
    • Member since 06-07-2003, 12:50 PM
    • Los Angeles, CA
    • Posts 1,186

    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

    01-16-2006, 9:29 PM
    • Member
      259 point Member
    • MNF
    • Member since 07-24-2005, 8:15 PM
    • Posts 72
    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

    01-16-2006, 9:38 PM
    • Contributor
      5,869 point Contributor
    • adefwebserver
    • Member since 06-07-2003, 12:50 PM
    • Los Angeles, CA
    • Posts 1,186
    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

    01-17-2006, 2:06 AM
    • Member
      259 point Member
    • MNF
    • Member since 07-24-2005, 8:15 PM
    • Posts 72
    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.
Page 1 of 1 (7 items)