tags:

views:

147

answers:

2

I want to end up with a single VS project/solution that I can check in to source control, that any other developer in the office can simply check out and run, and that I can deploy without having to install EPiServer program files on every web server.

I have just used the EPiServer 6 Deployment center (part of the official EPiServer 6 download). That gave me an EPiServer templates project, website setup in IIS, and a database installed.

The first issue is that when I change the VS project file to use the Visual Studio Development Server, the cms start page (site centre) no longer works.

And an even bigger problem is that the episerver.config file is using all sorts of files in the C:\Program Files (x86)\EPiServer directory on my machine.

A: 

You can remove the virtualPath items pointing to Program Files in the config file and copy those folders to the same paths inside the source controlled project folder.

Johan Kronberg
A: 

A colleague of mine wrote up a blog post about this.

Bartek Tatkowski
Thanks for the pointer. That's a very useful series which I'll be looking at again! Although it doesn't cover the problems of EPiServer having physical paths in it's configuration which will cause headaches when checking out code on another developer's machine, and deploying to web servers.
Jonathan Sewell