Gabe Sumner

Gabe Sumner

The RSS Feed URL cannot be found!
The remote server returned an error: (400) Bad Request.

Back to all posts

Upgraded from Sitefinity 3.2 to Sitefinity 3.5 SP1

This web site is now upgraded to Sitefinity 3.5 SP 1.  Compared to the issues I had upgrading to 3.2, this was a relatively easy upgrade process.  I did hit a few minor snags along the way though:

  1. Single Assembly for new ASP.NET AJAX Controls
    Sitefinity now includes the latest version of the ASP.NET AJAX RadControls.  Previously, each of these controls had its own assembly (DLL).  With the latest release, all of these assemblies have been combined into a single assembly (Telerik.Web.UI).  This is a great move and makes managing the files easier.  But some of my custom controls were referencing these old separate assemblies.  These references needed to be updated. 
  2. Migrate Customizations to Sitefinity ControlTemplates
    Any custom modifications made to the Sitefinity ControlTemplates needed to be manually merged with the latest release.  This process is not as easy as I would like it to be, but it's manageable.  Just keep track of the Sitefinity ControlTemplates you're changing.
  3. URLs for "Images & Documents" Resources Changed
    The URLs for my "Images & Documents" resources changed with this upgrade.  For example, previously my URLs looked like this:
  4. Minor Sitefinity API Changes
    There were a couple of minor Sitefinity API changes that caused errors.  The following lines of code previously worked with 3.2, but needed to be updated for the 3.5 release:
    • Telerik.DataAccess.CacheDependencyHandler.Current.Notify(typeof(Telerik.Cms.ICmsPage));
    • CmsRootSiteMapNode rootnode = (CmsRootSiteMapNode)ourMapProvider.RootNode;

    Not a perfect upgrade process, but it's getting a lot better.  We're beginning see the Sitefinity API & framework stabilize. 

    I have updated the Goondocks Sitefinity Controls to work with Sitefinity 3.5 SP1.  These controls, sadly, had fallen into disrepair.  They are now current and should work fine in your Sitefinity web site.

    With Sitefinity 3.6 we're looking at better upgrade & deployment options.  The upgrade process should continue to get easier.

    Facebook DZone It! Digg It! StumbleUpon Technorati Del.icio.us NewsVine Reddit Blinklist Furl it!

    Comments  4

    • Mtech 4 Nov, 04:00 PM

      I believe for "URLs for "Images & Documents" Resources Changed" you can control that in the web.config. Look under:
      cmsEngine
      providers
      add name=Libraries....>

      There is a path there.


    • Gabe Sumner 4 Nov, 04:11 PM

      Hey Mtech,

      You're correct. I didn't look closely enough. There is a "urlWhitespaceChar" property that I could change to " ".

      That being said I actually prefer the "_" and have now already altered my image pages.

      This might be a helpful suggestion for others though.

      Thanks for the comment.


    • Indianapolis Web Design 5 Nov, 09:15 AM

      Gabe,

      Thanks for the informative article! I wish I had come across it BEFORE our upgrade to Sitefinity 3.5 SP1.

      Send me an email and I will show you the SF projects that I am working on.

      -Dan Finney


    • mckeach 9 Dec, 03:48 PM

      So I would like the whitespace character to work as it did in 3.2 so I don't have to update links throughout my site. I have tried changing to:
      urlWhitespaceChar=" "
      and
      urlWhitespaceChar="%20 "
      instead of
      urlWhitespaceChar="_ " MTech did you ever get this to work and what exactly did your put in the web.config for urlWhitespaceChar


    Post a comment!


    HostMySite.com   website uptime