Hi everyone,

I would like to ask the group about their strategies for source controlling DNN Apps/Sites/Modules. We are evaluating developing some LOB modules and skins in a team of three. So far it has proved very difficult to synchronise code across our machines. Can any one share some tips? I have tried to Unbind the actual DNN website and keep the modules controlled but VS just adds the whole website back as new files.

Also compilation is very slow. Enabling debugging in web.config and adding the DNN website to build in configuration can give build times in the region of 40 minutes - not building up front means the website crawls along. Any advice here would be welcome as well. Sometimes I have noticed that there are two instances of vbc.exe running at the same time but this is not always the case.Machine specs: Dell Precision M65, dual core 2.33 Ghz with 4Gb ram running Vista x64 VS2008 same problems  on cuad core Precision 690, 4 gb ram, XP(32bit)  Vs2008

 any tips welcomed cheers jd

John,

Are you loading the full DNN source project when developing your module?

I use the methods found at http://vladan.strigo.net/projects/blankmodule-dnn-dev.-enviroment-setup-for-visual-studio-2005/ and use VS Source Safe mainly as a backup to my code but this allows me check in from my desktop and check out to my laptop if I need to take code with me.

I also find VS2008 very sloooow to compile. It even seems to hang for moments when I am typing code. I assume doing background compile/syntax checking. It seems a fast machine is no longer adequate[:(]

I wonder can a lot of the background stuff be turned off and just let us get on with typing code then let the compiler find the syntax errors at compile time? I must check this out..

---

I have many recommendations on this topic, far too much to put here in this post as I just finished a week long training session with a development team explaining my thoughts on the process....but I'll share a bit of insight on this.

First and foremost use the WAP development model, do NOT build your modules inside of DNN, you then do not have to build DNN and you can simplify debugging greatly, by only attaching the debugger for your specific module and not the entire DNN process.  I can build and debug a module on my system in under 20 seconds.

If you want some more information/discussion on this one drop me an e-mail msellers@iowacomputergurus.com

---

-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.


Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services