Last post Jun 10, 2005 01:21 PM by linguinut
Jun 09, 2005 12:15 PM|linguinut|LINK
Perhaps this has already been asked and discussed...or perhaps I am just a doofus...
Can I have one project containing several custom modules then assign them accordingly within DNN? What are some pros and cons of doing it this way? Will one project greatly limit me in some way? Will many projects (one per custom module) get too unwieldy?
Any input on this will be appreciated. I have a very large intranet application that I would like to start migrating to the DNN environment. I'd like to take the best path up front rather than half way through the trip and needing to backtrack. My plans
are not to go public with these mods, so bundling for public use is not a concern. If I ever got creative enough to think that other users could benefit from them, I would be glad to share. I will post some module concepts of mine in another thread.
Jun 09, 2005 01:29 PM|RLyda|LINK
Jun 10, 2005 01:21 PM|linguinut|LINK
One overall development Solution, one DotNetNuke Project, one BuildSupport Project, N Module Projects....this works just fine! Change your VS config to build just the module you're working on, to save compile time.