Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
The content you're reading is getting on in years
This post is on the older side and its content may be out of date.
Be sure to visit our blogs homepage for our latest news, updates and information.
The Sitefinity 4 Migration Module takes care of migrating pages and content items from Sitefinity 3. However, if you've done any custom development, such as custom user controls and modules that use the Sitefinity 3 API, you may find these controls need to be updated.
In Sitefinity 3, most of the components were spread out amongst several DLL files, each with their own separate namespace. Sitefinity 4 reduced many of these to a single Telerik.Sitefinity.dll file so that all CMS classes share that common namespace.
This new API helps organize the Sitefinity namespaces. In Sitefinity 3, each module had a top-level namespace, such as Telerik.Blogs and Telerik.News. Sitefinity 4 places all of these modules under a new Telerik.Sitefinity.Modules namespace. Any additional required components of a module, such as Data Models, Configuration, and Widgets exist underneath their respective namespace.
Another advantage to this approach is a simplified upgrade path, reducing the number of libraries that need to be updated. If you are developing custom components, you only need the main Telerik.Sitefinity namespace to access most of the major components of Sitefinity.
Instead of trying to create a definitive list of API changes, this post will instead highlight the major areas of documentation that developers coming from Sitefinity 3 will find useful.
Pages are organized as just another Sitefinity module, with their own Content Manager and API. If your custom controls and modules are accessing pages programmatically, you'll definitely want to look at the Sitefinity 4 Pages Documentation. Examples for the topics below are available using both the native content manager and the new Fluent API.
Content items such as News, Blog Posts, Events, etc. can be retrieved and manipulated using either their associated Content Manager or the new Fluent API. The Sitefinity 4 Modules Documentation includes examples of both methods for each native module.
The simplest way to extend Sitefinity 4 is by creating a User-Control-based module. This means that all of the logic and user-interface components are contained in User Controls (.ascx files) that you place directly on a page. There are two options for this type of module:
You can also Sitefinity by making your own Content-based module, tying deeply into things like taxonomy, lifecycle, workflow, and permissions. This is a more advanced topic, and is available in the blog post series Creating Content-Based Modules.
However, the 4.4 release of Sitefinity will include a new Module Builder, that allows you to create new Content types (including all native Sitefinity features such as workflow, taxonomy, etc.) on the fly right inside of Sitefinity. More details will be available in Q1 after the release.
Widgets in Sitefinity 4 are still based on standard ASP.NET controls (.ascx files). However, there have been some changes to creating user-friendly control designers. For a detailed look at the process of creating several different types of Sitefinity 4 widgets, from simple to advanced, take a look at the following topics:
Here I hope to briefly list some common changes that have been frequently asked about by customers. This is by no means an exhaustive list, but I will update it based on feedback via our Sitefinity Discussion Forums. If you are having trouble locating something from Sitefinity 3, please feel free to submit a post so that I can update this section.
While in Sitefinity 3, the main SiteMenu was a standard user control (ascx file), the navigation control in Sitefinity 4 is now a compiled web control. So if you wish to add the Sitefinity menu to a custom user control, you need to register it first, as shown here.
<%@ Register Assembly="Telerik.Sitefinity" Namespace="Telerik.Sitefinity.Web.UI.NavigationControls" TagPrefix="sf" %>
<sf:SiteMenu ID="SiteMenu1" runat="server" />
Although the breadcrumb control is planned to be included in the Sitefinity 4.4 release, you can recreate it now by following this blog post Working Breadcrumb Widget With Source.
Alternatively, you can add the standard ASP.NET breadcrumb control, as described by Ivan's first reply to this thread: Breadcrumbs in SF4.
View all posts from The Progress Team on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.