EPiServer are currently developing an integration module with SharePoint 2007/WSS 3.0.
Phase 1 will see the ability to publish content from SharePoint to EPiServer with Phase 2 the ability to present content within SharePoint from EPiServer.
This module is being built to run with EPiServer CMS.
More information can be found here including how to sign up for the beta testing:
http://www.episerver.com/en/EPiServer_Knowledge_Center/Developer-Forum2/EPiServer-Developer-Forums-/SharePoint-EPiServer-Integration-Module/Info-SharePoint-EPiServer-Integration-module/
Friday, 29 June 2007
Tuesday, 19 June 2007
Fiddler
Yesterday I was having some performance problems with one of my MCMS websites and a workmate pointed me towards a tool he found. It's called Fiddler.
Fiddler is a http debugger which logs all http requests between your computer and the Internet. You can then check out the http traffic and inspect ingoing/outgoing data.
Quite an interesting tool, check it out here: http://www.fiddlertool.com/fiddler/
Fiddler is a http debugger which logs all http requests between your computer and the Internet. You can then check out the http traffic and inspect ingoing/outgoing data.
Quite an interesting tool, check it out here: http://www.fiddlertool.com/fiddler/
Monday, 18 June 2007
It's ALIVE
After only 3 failed installations I finally have an EPiServer CMS 5 demo site up and running - hurray!
I learnt quite a few things while completing this installation.
First of all you can install the site using either the EPiServer manager install (like we're used to with EPiServer 4.*) or by using the extensions within studio to create a new project. I found the EPiServer manager install more useful this time around as it installs some sample templates. For future projects a clean install through studio will be beneficial.
The EPiServer manager install can fail a few times and the forums are a good place to find resolutions to problems during this step. My issues were due to dll access (not rolling back completely after a failed install) and sql server 2005 problems. A very common error is remote connections not enabled:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
For this issue you need to configure remote connections within the Surface Area Configuration Tool. The following is a good resource: http://support.microsoft.com/kb/914277
This documentation (http://www.episerver.com/en/EPiServer_Knowledge_Center/Documentation/Release-Notes-CMS-Beta/EPiServer-CMS-5-RC1-Revised-Documentation/Setting-Up-a-New-EPiServer-Site-with-Visual-Studio/) details how to set an episerver site with visual studio. If you install the site through the manager you can skip the first few steps although you will want to make sure your project and solution are all created and compiling correctly at this point.
The documentation is also available within the SDK. The EPiServer CMS 5 SDK can be found within your Start/All Programs if you have used the sdk installation package.
From here you can follow the documentation on Creating Roles and Users in the above link.
Note: there is one important thing missing from the documentation. Before you create the roles and users you need to run the ASP .NET SQL Server Registration Tool - Aspnet_regsql.exe (see http://msdn2.microsoft.com/en-us/library/ms229862(vs.80).aspx). This will allow you to install the database elements for the membership and role management. There has been mention that you can install your users and roles anywhere but for ease in your demo site I suggest installing on your demo database.
Once the reg tool has been run you can follow the steps to create the roles and users.
With all the hard setup parts done you can now login using sitename/util/login.aspx and the user you just created. I had a few configuration issues at this point. One of them was I had to have the entry applicationId="/LM/W3SVC/10/Root" as an attribute of my site tag:
site applicationId="/LM/W3SVC/10/Root" description="Example Site"
Afterwards, the site compiled correctly, I could login to admin and edit modes and I finally had a working demo site to play with.
- Workflow foundation, themes and role management here I come :)
I learnt quite a few things while completing this installation.
First of all you can install the site using either the EPiServer manager install (like we're used to with EPiServer 4.*) or by using the extensions within studio to create a new project. I found the EPiServer manager install more useful this time around as it installs some sample templates. For future projects a clean install through studio will be beneficial.
The EPiServer manager install can fail a few times and the forums are a good place to find resolutions to problems during this step. My issues were due to dll access (not rolling back completely after a failed install) and sql server 2005 problems. A very common error is remote connections not enabled:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
For this issue you need to configure remote connections within the Surface Area Configuration Tool. The following is a good resource: http://support.microsoft.com/kb/914277
This documentation (http://www.episerver.com/en/EPiServer_Knowledge_Center/Documentation/Release-Notes-CMS-Beta/EPiServer-CMS-5-RC1-Revised-Documentation/Setting-Up-a-New-EPiServer-Site-with-Visual-Studio/) details how to set an episerver site with visual studio. If you install the site through the manager you can skip the first few steps although you will want to make sure your project and solution are all created and compiling correctly at this point.
The documentation is also available within the SDK. The EPiServer CMS 5 SDK can be found within your Start/All Programs if you have used the sdk installation package.
From here you can follow the documentation on Creating Roles and Users in the above link.
Note: there is one important thing missing from the documentation. Before you create the roles and users you need to run the ASP .NET SQL Server Registration Tool - Aspnet_regsql.exe (see http://msdn2.microsoft.com/en-us/library/ms229862(vs.80).aspx). This will allow you to install the database elements for the membership and role management. There has been mention that you can install your users and roles anywhere but for ease in your demo site I suggest installing on your demo database.
Once the reg tool has been run you can follow the steps to create the roles and users.
With all the hard setup parts done you can now login using sitename/util/login.aspx and the user you just created. I had a few configuration issues at this point. One of them was I had to have the entry applicationId="/LM/W3SVC/10/Root" as an attribute of my site tag:
Afterwards, the site compiled correctly, I could login to admin and edit modes and I finally had a working demo site to play with.
- Workflow foundation, themes and role management here I come :)
Friday, 15 June 2007
Download EPiServer CMS 5 RC2 now
As anyone in the EPiServer community will know, EPiServer CMS 5 is the next generation of the EPiServer project and the release candidates are here. A couple of weeks ago RC2 was made available for download.
You can find the release notes and other interesting information here: http://www.episerver.com/en/EPiServer_Knowledge_Center/Documentation/Release-Notes-CMS-Beta/
There are a lot of changes in EPi5 and it'll take too long for me to list them all here, but in the next couple of months I plan on researching all of them and listing any interesting points and things I've learnt. I'm especially interested in the new integration with .net framework 3.0 and the windows workflow foundation. I consistently have questions about workflows from existing and potentional clients and I'm excited to see what the new workflow components can do.
I'm interested to hear from anyone else who is researching EPi5 and how you are going with installs and getting it all setup.
You can find the release notes and other interesting information here: http://www.episerver.com/en/EPiServer_Knowledge_Center/Documentation/Release-Notes-CMS-Beta/
There are a lot of changes in EPi5 and it'll take too long for me to list them all here, but in the next couple of months I plan on researching all of them and listing any interesting points and things I've learnt. I'm especially interested in the new integration with .net framework 3.0 and the windows workflow foundation. I consistently have questions about workflows from existing and potentional clients and I'm excited to see what the new workflow components can do.
I'm interested to hear from anyone else who is researching EPi5 and how you are going with installs and getting it all setup.
Hello World
My first blog entry... incredibly exciting. I have been thinking of starting a blog for awhile now and I've realised thinking is not doing so here I am.
I have been developing with EPiServer, a content management system (www.episerver.com) for probably over a year now and I have found a true passion for the web industry. This blog is going to feature all things EPiServer -
News
Code Samples
Interesting tid-bits
Tips and Tricks
Just to make things interesting expect to see me throw in the odd post around other web technologies or random thoughts I have about development work in general.
Enjoy, please feel free to post a comment or thought. See you again soon :)
I have been developing with EPiServer, a content management system (www.episerver.com) for probably over a year now and I have found a true passion for the web industry. This blog is going to feature all things EPiServer -
News
Code Samples
Interesting tid-bits
Tips and Tricks
Just to make things interesting expect to see me throw in the odd post around other web technologies or random thoughts I have about development work in general.
Enjoy, please feel free to post a comment or thought. See you again soon :)
Subscribe to:
Posts (Atom)