How to setup a development enviroment for many users

Leo Leme asked on November 12, 2015 21:11

Hello, I’m new with Kentico.

I’m a developer for a long time. I’m trying to understand how does kentico works.

I don’t understand, for example: . Can me and my team could work with source safe ? So each one of us can change the code locally and then send the changes to source safe so everyone will get the changes ? . When I send a new webpart for staging, what does it means ? Does the ascx.cs file is copied to the staging server ? . When Kentico publishes the website, does it makes a complete compilation of the website ? . I understand that a lot of configurations are in Kentico’s database. Does it involves the c# code ?

Well, if anyone could answer these questions it would be very nice.

Thank you very much !

Recent Answers

Rui Wang answered on November 12, 2015 22:02 (last edited on November 12, 2015 22:02)

Leo, this documentation can help you understand a lot of the questions you have

Also, this whitepaper has a chapter on development which can help you as well.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on November 12, 2015 22:03

Regarding setting up your environment, I and other Kentico dev/partners do this all the time. V9 has many more CI improvements coming out specifically for this. What I do is have one person create the site initially and check it into source control. The database is typically remote either in the cloud or on your local network.

When you "send a new webpart to staging", if you're using the Staging app, this will simply send the configuration of the webpart over and not the physical files. You will need to either FTP those files or export and import those. Or use your CI tools to do so.

Technically, Kentico doesn't publish your site, you or some other process does. Kentico is simply an ASP.NET website with a bunch of awesome features.

Yes Kentico has a lot of configuration options within the UI and yes they are all stored in the database. You can use your web.config to store these values but they typically vary from dev, to staging to live. So it's ideal to create your own custom settings which you can configure within the UI which is supported and very easy to do. Creating these database driven settings do not require any C#.

2 votesVote for this answer Mark as a Correct answer

   Please, sign in to be able to submit a new answer.