Development environment

Chosing a development strategy

The way you set up your development environment can influence the way you build and deploy your EPiServer solution. The way you deploy your solution could well be influenced by how you set up the initial development environment. In the following we describe benefits and disadvantages for some common development strategies.

Creating a project from Visual Studio using the EPiServer project template

• You will have a project that you can check-out on other machines without bothering about configuring IIS since IIS Express is used by default.
• You will be creating a clean installation without any templates.
• The project will be configured with NuGet dependencies to make it easy to upgrade to the latest version of the EPiServer platform [New in 7.6]

Creating a solution based on sample templates from Deployment Center

• An IIS application is created and you can select a remote database server.
• The site is detected in Deployment Center which is beneficial if you are using any additional EPiServer modules that requires Deployment Center to be installed .
• You will have  a set of sample  templates on which you can continue to develop upon. Using the sample templates you will have an project advanced starting point.

Creating an empty website from Deployment Center

• An IIS application is created and you can select a remote database server.
• The site is detected in Deployment Center which is beneficial if you are using any additional EPiServer modules that requires Deployment Center to be installed .
• You will be creating a clean installation without any templates, which can sometimes be desirable.

See also

• Deployment Center
• Deploying EPiServer CMS sites
• Deployment scenarios