If, like me you've developed an EPiServer site using their new Visual Studio 2005 Project you may have become frustrated when coming to install it on your Live server using EPiServer Manager. For those of you that haven't, i'm referring to the bit of the install where it asks you which Module you want to install. Module? What's a Module? If you don't select one you need to install the demo site - which no one wants to do when they've just spent time creating their real site in a development environment.

After a bit of digging (i couldn't find any info on EPiServer's site) i worked out that a Module was simply a zip file! So i Zipped up my ASP_Theme folder, all my user controls, pages and language files (i left the web.config out) and copied it to the server. Then at the end of install through EPiServer Manager I chose "install module" and selected my zip - then hey presto it installed my developed site!

The next annoyance to overcome was the "now you must install basic content" option ( /admin/setup.aspx) which will only let you select to install the demo site's data... after more digging i found that this is simple too. Login to the admin page of your development site and export all data (pages types, tabs, categories etc etc) Then save the export file (give it a meaningful name) into "[WEBSITE]\Util\setup\" folder (you will probably need to create the folder) then refresh the setup page - and hey presto again - you'll now have the option to install your data rather than the demo!

In fact i'd recommend adding the .episerverdata created via the export tool to your original zip file to make the process even more streamlined.

Out of interest does anyone know how to disable the setup.aspx page from appearing? until you've ran it you can't see your page as IIS serves the setup.aspx instead (even if you've restored a database or pointed it to an exiting one)

Bookmark with :
Digg It! DZone StumbleUpon Technorati Reddit Del.icio.us Newsvine Furl Blinklist
posted @ Wednesday, December 12, 2007 11:00 AM | in C# EPiServer

Comments

Gravatar
# re: Installing Visual Studio 2005 project via EPiServer Manager
Posted by Steve Celius
on 12/13/2007 9:49 AM
I think the setup page will be shown as long as you have no start page id in web.config. It indicates that the site does not have any content, and that EPiServer should ask for some.

From CMS 5 SP1 you'll be able to put an .xmlupdate file too in the package, and it will add, change or remove settings in your web.config file.

I think this feature is great for module deployment too, and definitively something I'll look into for the modules on EPiCode.

/Steve
Gravatar
# re: Installing Visual Studio 2005 project via EPiServer Manager
Posted by Eric Pettersson
on 12/14/2007 1:07 PM
Hi, when I develop episerver cms sites i only install a site on the server without any content and db. Then I copy my templates and dlls to the server. After that I install the db on the server. Make the correct changes in the web.config-file and after that, the site is up and runnig.
Gravatar
# re: Installing Visual Studio 2005 project via EPiServer Manager
on 3/5/2008 2:50 AM
I have just come across this process myself. I am creating a .xmlupdate file for the deployment and I've worked out how to add and delete settings but not how to change. Have you managed to get this working and know the syntax that's required?

Post Comment

Title *
Name *
Email
Url
Comment *  


Please add 1 and 6 and type the answer here: