On most Episerver builds, you will be working within a team of developers. There are a number of different ways on how to structure your Episerver deployment process. In some scenarios, having a shared database works really well, in some instances, you may want each individual developer to have their own database.
If you go down the route of each developer having their own local database, then you'll encounter the issue of config files and source control. In today's tutorial, I'm going to cover a strategy to enable each developer in your team to have their own custom connection string config file stored in source control, without affecting anyone else. When you have to deal with multiple developers in a project, I suggest you split your web.config up and move your connection string settings to a separate config file. You can do this like so:
<?xml version="1.0" encoding="utf-8"?>
<add name="EPiServerDB" connectionString="user id=dev;password=password;Data Source=DEV\.;Database=DeveloperOneEpiserverDb" />
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
<Output TaskParameter="Lines" ItemName="TransformedWebConnectionStrings" />
<Output TaskParameter="Lines" ItemName="UnTransformedConnectionStrings" />
<Copy Condition=" @(UnTransformedConnectionStrings) != @(TransformedWebConnectionStrings) "
Software Architect, Programmer and Technologist Jon Jones is founder and CEO of London-based tech firm Digital Prompt. He has been working in the field for nearly a decade, specializing in new technologies and technical solution research in the web business. A passionate blogger by heart , speaker & consultant from England.. always on the hunt for the next challenge