Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Setup for Multiple DevelopersSetup for Multiple Developers
Previous
 
Next
New Post
11/8/2007 9:25 AM
 
Stephen

Joined: 11/7/2007
Posts: 10

New to DNN.  We were able to sucessfully install DNN on a developer's machine.  The database was created in  SQL Server 2005 on a shared server.  The dev environment was setup in VS 2005.

We are now ready to install the dev environment on other developer machines.  Is there anything special to do?  I had concerns about running through the full install again because I am thinking it isn't smart enough to know that the database portion has already been installed.  Am I wrong?

We will be storing all module development (and probably the whole website) in source control in order for developers to work on different pieces. 

Are there any guidelines for setting this up for multple developers?
 
New Post
11/8/2007 9:45 AM
 
Brian Dukes


Brian Dukes's Avatar

Brian Dukes's Avatar

www.engagesoftware.com
Joined: 8/25/2006
Posts: 896

Are you using the installer, or the DNN Source or Install package?

We typically set up different databases for each developer so that one can't get stuck with a database that doesn't work with his code if another developer has changes checked out.  This means that your developers will have to make sure that SQL scripts are re-runnable, (that they check for existence of objects before trying to create or drop, that sort of thing) so that they can run each others changes for the same script.

So far as the environment goes, if you're doing seperate databases it's pretty easy, just do what you've already done.  If you want to stick with the single database model, you should be able to just unzip the Install or Source package (or just copy the file structure from the first developer's machine), set it up with the correct ACL security and in IIS, and you should be good to go (it'll see the database the same as any other already setup website would).  Just make sure that you add the new developer's URL as a Portal Alias if it's different.

Let me know if that makes sense,

Brian Dukes
Engage Software
St. Louis, MO
866-907-4002
DNN partner specializing in custom, enterprise DNN development.
 
New Post
11/8/2007 9:59 AM
 
Stephen

Joined: 11/7/2007
Posts: 10

Brian Dukes wrote

Are you using the installer, or the DNN Source or Install package?

We used the 4.7 starter kit to setup the first machine.  Well actually we are having some install issues, but that is beside the point of this thread.  I am with a team that has been developing a custom web application for our company for many years.  I am used to everything being maintained within a single solution that is in VSS.  We have an Oracle backend.  Multiple developer setup is a synch.  When you want the latest working version of the app, we simply do a get latest.  We all point to the same dev databse.

I am not sure if doing module development in DNN is any different.  I might be working on Module 1 while someone else is working on Module 2.  I could see potential problems if dev 2 does some db changes to the central database that affects his module while he is developing.  If he in turn doesn't check in his work and proceeds to add a page to the web app to test his new module, I would have a problem if I try to run the version of the module I have on my machine.  This is similar to issues we have now in our other app, so we are okay with it.

The million dollar question (since I still have to learn more things about module development) is when I am finsihed with my new or enhanced module, how do I test my module code?  Is it as simple as running the site in debug mode and putting breakpoints in my module code?

The setup I was thinking was that each developer would have the .net solution on their local dev machines, but point to a central SQL Server database.  Is there problems or concerns with how DNN creates tabid's and such to work like this?
 
New Post
11/9/2007 7:57 AM
 
Andrew Ross


Joined: 3/4/2004
Posts: 46

The way we do it here is, we all have a local copy of the install version of dnn, and we all run off the same db.  We use Visual Source Safe 2005, and we have only 5 developers so its pretty easy to maintain.  I have not ran into any issues running it this way as to date, and this has been working for about 6 months for us.  To me it makes more sense that everyone runs off a central db, so that everyone sees the same content and pages, especially if you are linking to other pages within your module.  I have worked with DNN extensively for at least 5 years now, and this is the best way i have been able to work with it in a multi user environment.

JL Systems
(DNN Site Examples)
American Holistic Nurses Association
Greater Reston Chamber of Commerce
Financial Planning Institue of Southern Africa
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Setup for Multiple DevelopersSetup for Multiple Developers


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