June 3, 2008 by Alistair Deneys
I was privileged enough to be included in the Crestone beta program which Sitecore ran recently. Crestone is the code name of the new Sitecore release. This release is an evolutionary upgrade with a strong focus on usability. This is evident in the new page editor and page designer interfaces.
Off the UI, the most immediately evident changes are the number of databases (only master, web and core now) and the new security model. The security model in Sitecore now uses ASP.NET security.
My first interactions with Crestone were at the API, when I had to update Revolver to work with the new release. Following are some of the changes I had to make to get Revolver kicking on Crestone.
- There is no longer a GetRole method on the Domain class
- There is no Sitecore.SecurityModel.Domain class. It has been moved to Sitecore.Security.Domains.Domain class.
- Domain class doesn’t have a login method anymore. Use Sitecore.Security.Authentication.AuthenticationManager.Login() which returns a bool instead of a DomainAccessResult.
- SecuritySwitcher not in Sitecore.SecurityModel anymore. Use Sitecore.Security.Accounts.UserSwitcher.Enter instead.
- No logout on domain, use Sitecore.Security.Authentication.AuthenticationManager.Logout() instead.
- PublishOptions constructor no longer takes 3 parameters, only 5. Must include the source and target databases.
As you can see from the above, most of the updates I had to make were to do with the new security model. Another notable change is that there are no longer masters, however, APIs to interact with masters are still present.
Now is the time to start going over your code and changing any usage of deprecated methods. I haven’t yet analysed if any methods have been removed which were deprecated in Sitecore 5.3.x, but this is the purpose of the deprecated attribute. To warn us developers that the object could be removed in a future release.