Coordinator
Nov 22 2011 at 1:10 PM
Edited Dec 20 2011 at 1:17 PM
|
NOTE: If you're running on C1 3.0 RC2 or RC3, there's a free upgrade package available, see details
here
Requirements for upgrade
1. Your site should already be running on C1 2.1.1 or newer version
2. Visual Studio 2010
3. A tool for mergin code files. Recommended software is TortoiseMerge, it's free and can be download as a part of TortoiseSVN (http://tortoisesvn.net/downloads.html)
Upgrade steps:
0. Remember to create a backup copy of your site. Stop the related application pool on IIS/WebMatrix before upgrading.
1. If you don't have TortoiseMerge installed, download and install it as a part of TortoiseSVN (http://tortoisesvn.net/downloads.html)
2. Download & build C1 version you're going to upgrade to
C1 v3.0 RTM
http://compositec1.codeplex.com/SourceControl/changeset/changes/10372
3. Merge changes to web.config.
Use Visual Studio (or another text editor) to format your site's web.config. In VS the hotkeys are Ctrl+A, Ctrl+K-F
Download web.config versions for C1 2.1.1 and C1 3.0 RTM
http://docs.composite.net/Downloads/UpgradeFiles/3.0/web6706.xml
http://docs.composite.net/Downloads/UpgradeFiles/3.0/web9387.xml
Run TortoiseMerge to merge the changes. The setup is:
"Base file" = web6706.xml (web.config from 2.1.1)
"Their file" = web9387.xml (web.config from 3.0 RTM)
"My file" = web.config from your site
Most of the changes likely will be merged automatically, resolve the conflicts and save the merged file
4. Perform the same steps to merge changes to file /App_Data/Composite/composite.config
Format xml in Visaul Studio Download composite.config versions for C1 2.1.1 and C1 3.0 RTM
http://docs.composite.net/Downloads/UpgradeFiles/3.0/composite6706.xml
http://docs.composite.net/Downloads/UpgradeFiles/3.0/composite9387.xml
Before running mergin tool edit the config file and move section "loggingConfiguration" to the bottom of the file
...
<loggingConfiguration name="Logging Application Block" tracingEnabled="true" defaultCategory="General" logWarningsWhenNoCategoriesMatch="true">
....
</loggingConfiguration>
</configuration>
Run TortoiseMerge to merge the changes. The setup is:
"Base file" = composite6706.xml (composite.config from 2.1.1)
"Their file" = composite9387.xml (composite.config from 3.0 RTM)
"My file" = /App_Data/Composite/composite.config from your site
5. Updating files & folders.
Copy from the new site (and override if necessary) the following files:
\default.aspx
\App_Data\Composite\Configuration\UrlFormatting.xml
\App_Data\Composite\TreeDefinitions\UrlConfiguration.xml
\Bin\Composite.dll
\Bin\Composite.Workflows.dll
\Frontend\Config\VisualEditor\common.xml (merge custom changes if needed)
\Frontend\Config\VisualEditor\Styles\core.css
Delete the following file:
\App_Data\Composite\Configuration\XmlDataProvider.config
Copy and override all the files from the following folders (note: not
including subfolders)
\Composite\*.*
\Composite\localization\*.*
\Renderers\*.*
Delete and copy the following folders
\Composite\content\
\Composite\controls\
\Composite\flash\
\Composite\images\
\Composite\services\
\Composite\scripts\
\Composite\schemas\
\Composite\skins\
\Composite\styles\
\Composite\transformations\
\Composite\templates\
5. [Not needed while upgrading from C1 2.1.3 or newer version]. If “Composite.Community.Blog” or “Composite.News” are installed, download and replace related dlls:
http://docs.composite.net/Downloads/Temp/2.1.3Beta2/Composite.Community.Blog.dll
http://docs.composite.net/Downloads/Temp/2.1.3Beta2/Composite.News.dll
6. [Not needed while upgrading from C1 2.1.3 or newer version]. Upgrade steps for Composite.Contrib project:
a) Uninstall Contrib package.
b) download a newer package file Contribution.CompositeC1Contrib.Core/Release/Contribution.CompositeC1Contrib.Core.zip from
http://c1packages.codeplex.com/SourceControl/changeset/changes/8618
c) In C1 Console find System -> Packages -> Installed packages -> Local packages, right click choose "Install local package" and choose the package you downloaded in the previous
step
We hope you'll like the changes and we're looking forward to hearing your feedback
|