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.0Multi-module + Multi-developer setupMulti-module + Multi-developer setup
Previous
 
Next
New Post
6/22/2009 2:32 PM
 

These may be mutually exclusive questions but let me explain the situation I am in.

I am developing an complex application that consists of three modules. These three modules would likely share the same data layer, but the business logic and UI is totally different. I've seen some modules out there that actually are a collection of modules when installed. My wish is to do the same, 3 modules sharing code.

The other part to this puzzle is that I need to be able to develop with another person, so some sort of source control would be necessary. Ideally, one person would work on one module 1 and another would work on module 2.

How do we set up the solution correctly and how do we keep from stepping on each others toes? Currently, I have one module started using these setup instructions: http://www.ericduhaime.com/wiki/pmwiki.php/Programmation/StepByStepSetupOfVS2005Project

Thanks for any insight.

 
New Post
6/22/2009 3:03 PM
 

Erik,

Well first of all you are 100% correct that source control is a good idea.  I personally recommend SourceGear's Fortress product as it is source control and bug tracking.

As for the structure, I would try to work with a central data layer, and then the modules.  I would try to divide the work in a manner that separates work, and prevents you from both working on the same code.


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

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
 
New Post
6/23/2009 8:37 AM
 

Thanks Mitch. I'll check out source gear

I think what I need to know is how we create the solution properly.so we can have a central data layer and share some business objects. This is the first project that I have tackled that is both nulti-module in nature and requires another developer.

Thanks,

E

 
New Post
6/23/2009 4:05 PM
 

Ok here is the path I'm going down.

1. I'm going to turn this into a dynamically compiled module (AppCode) rather than a WAP. I figure it will be easier for us to use and colloborate on the data layers this way rather than compiling changes constantly.

2. The modules will all belong to the same shared project. Techinically, the module definition is what defines what controls are loaded. So one VS project with 3 module definitions. The module will not be redistributed beyond the one installation anyways.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Multi-module + Multi-developer setupMulti-module + Multi-developer setup


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