Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN DebuggingDNN Debugging
Previous
 
Next
New Post
1/18/2007 11:06 AM
 
Does anybody know a way to speed up the build time for DNN.  When trying to debug in VS2005, it takes forever to rebuild the DNN solution. I am open to any suggestions.
 
New Post
1/18/2007 4:19 PM
 
you should usually not need to rebuild DNN, only your module. have a look at the tutorials from Michael Washington, how to setup your IDE.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
1/18/2007 9:22 PM
 

I create Module for DNN everyday and I debug constantly. I also have very little patience. So here is what works for me:

I use either of these set-ups:

  • Setting-up the Environment (using IIS)
  • Setting-up the Environment (without IIS)
  • I use "using IIS" when I have a module that is one of a kind and part of a site that I have a live version on my public server. For all others I use the "without IIS"

    For my "without IIS" modules I create a separate installation (using SQL Server Express) for each one. It takes less than 2 minutes to set up "without IIS".

    The Development environment only has DotNetNuke with the HTML module and the module I am working on. This debugs fast and easy. I can easily back up the App_Code and Desktopmodules folders for versioning.

    On my Windows XP machine at home I have about 20 folders of modules I am "working on". When I decide to work on a module I open Visual Studio (or Visual Web Developer Express) and then go to FILE then OPEN WEB SITE. The site opens and I start coding. To debug I simply click the debug button and it works.



    Michael Washington
    http://ADefWebserver.com
    www.ADefHelpDesk.com
    A Free Open Source DotNetNuke Help Desk Module
     
    New Post
    1/19/2007 5:59 AM
     
    Hi Michael,

    Out of interest, how long does your site take to reload after you make a change (without attaching the debugger?)
    I use Vladan's WAP model so buildtime is a couple of seconds, but it's the site reload time after each change that takes about 1 minute... very frustrating - not sure if it's the amount of assemblies in the bin or what....

    Entrepreneur

    PokerDIY Tournament Manager - PokerDIY Tournament Manager<
    PokerDIY Game Finder - Mobile Apps powered by DNN
    PokerDIY - Connecting Poker Players

     
    New Post
    1/19/2007 8:27 AM
     

    [QUOTE]rodneyjoyce wrote
    Out of interest, how long does your site take to reload after you make a change (without attaching the debugger?)
    QUOTE]

    With either of the two methods I indicated you simply save the page (even if it's a class file in the app_code directory) and then refresh the page in your web browser. It usually takes 3 seconds for a normal page to recompile page and 10 seconds for a file in the app_code directory (because all the files in a single directory in the app_code need to recompile because they are compiled in one assembly).

    The entire site does not have to reload. Only the change you made. Also for any file not in the app_code directory you can use "Build Page" to just compile that page to detect any changes and it only takes 3 seconds (with pages in the app_code your only option is "Build Site" this puts you into a full recompile so when yu can you just want to simply save the page and refresh your web browser).

    I have used the WAP method and yes it always compiles in about 3 seconds, but then the entire DNN site has to reload and for me it was 20+ seconds.



    Michael Washington
    http://ADefWebserver.com
    www.ADefHelpDesk.com
    A Free Open Source DotNetNuke Help Desk Module
     
    Previous
     
    Next
    HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0DNN DebuggingDNN Debugging


    These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

    For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

    1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
    2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
    3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
    4. No Flaming or Trolling.
    5. No Profanity, Racism, or Prejudice.
    6. Site Moderators have the final word on approving / removing a thread or post or comment.
    7. English language posting only, please.
    What is Liquid Content?
    Find Out
    What is Liquid Content?
    Find Out
    What is Liquid Content?
    Find Out