I have a number of modules that I've been building for various sites and I'm working with DNN 4.9.4.

I'm finding that if I change a line of code and hit debug to run the app ... the compile goes off into outer space for sometimes upto 1/2 hour befor finally finishing and allowing me to proceed with debug activities. 

I'm using a decent dev duel core laptop with 2G ram ... the processor and memory are not throttled - but the builds take forever ... to the point that it's just about driving me mad.

Any advise - or has anyone else experienced this?

I'm  using the dev model where code files are placed into project subfolder within App_Code and UI elements are in user controls in project sub-folder within DeskTopModules...yes inheriting from DotNetNuke.Entities.Modules.PortalModuleBase and all that .. the modules work great once compiled ... just painfully slow to debug and compile!

Help !

- Don

We build our modules by referencing only the DotNetNuke.dll file and don't include any other DotNetNuke core files in our project.

The downside is that you can't really debug the module using the built in debugger.  The upside is that the modules build in no more than a few seconds.

Don't use the debug run button, Start your localhost website in the browser and then use "Debug>attach to Prcess" then link to the "aspnet_wp.exe".

in the "Build>configuration manager" deselect all the build options on projects.  When you want to compile a project right click on the project and select build.

This way you only going to build the project you want to compile.

Regards,

Dave.