Currently there is no easy way of installing Community on top of a existing CMS installation. Therefore the easiest way is to do like this:
Seems like a lot of work, but actually it is done pretty quick. If you are several persons in the development team I advice you to use a common database and have your own site set up on each of the development machines. Personally I prefer to use the IIS, but Cassini will work just fine.
Great. I will try this approach. Maybe give feedback later on.
Oh, and yes, we do use common databases, cassini, subversion and set upp VPP on UNC shares such as \\server\vpp\project\global\.
As this is related to first time installs maybe you know why the following is happening?
I have not had a chance to investigate this.
When clicking on the 'Members' page a script error appears in the bottom bar of IE. not a very useful err description of "Line 2 char 1 syntax err." any clue..?
If I've installed Relate + 'EPiServer RelatePlus 126.96.36.199'. Will the 'Install Hotfix 1 for EPiServer Community 3.2' be included?
When I downloaded the install there was no hotfix listed so would assume so.
Thanks for that. I have updated the site with the hotfixes..
Do you perhaps have some idea about my previous Q on the script err:
"When clicking on the 'Members' page a script error appears in the bottom bar of IE. not a very useful err description of "Line 2 char 1 syntax err." any clue..?
After some investigating my suspicion is that it's the Ajax.. part of it.. but not sure yet..
<asp:UpdatePanel /> used on the page..
I have removed the update panel to try and isolate the script error.it's within there that it happens somewhere..
Narrowed the script error down to the control:
<RelatePlus:Members ID="ucMembers" runat="server" PageSize="12" OnMembersChanged="ucMembers_OnMembersChanged" />
this may make sense:
XML tag name mismatch (expected meta) createCallback()("")ScriptRe...=66d72566 (line 5) Members.aspx?_TSM_HiddenField_=ctl00_RelateScriptManager_HiddenField&_TSM_CombinedScripts_=%3b%3bAjaxControlToolkit%2c+Version%3d3.0.20229.20843%2c+Culture%3dneutral%2c+PublicKeyToken%3d28f01b0e84b6d53e%3aen%3a3b7d1b28-161f-426a-ab77-b345f2c428f5%3ae2e86ef9%3a1df13a87%3a8ccd9c1b()()
have got to the bottom of this. In the relate+ package calls such as
will not function correctly with strict firewall rules..
Following on from the initial post is there a best practice method for deploying a relate+ website into a production environment? i.e. once I have added new attributes - at the moment I am having to manually add these to each machine that install it onto.
Many thanks in advance
What are the best practices for performing a clean install of CMS 5 and Relate+ (Community and EPiMail) for local development purposes (Vista, VS2008 and Cassini)? No demo templates and our own namespace.
My guess is this in general:
1. Community 188.8.131.52 - "Install site and SQL Server database" (with EPiServer CMS integration) on staging server
2. Install EPiMail somehow (copying from other installation)
3. Copy everything locally
4. Create empty project and add references to EPiServer assemblies and modify web.config.
Or is there an easier way to get everything cleanly installed?