API changes in Sitefinity 7.1

• IPropertyChangeDataEvent.ChangedPropertyNames changed to ChangedProperties of type IDictionary<string, string,>
• Some of the IFormEntryEventControl properties are moved up the hierarchy into the newly introduced IFormEntryEventControlBase base interface, which is shared with the new IFormEntryValidationEventControl interfaces. This changes are source compatible, but as they are binary incompatible, a rebuild is required.
• Some of the ILoginCompletedEvent properties are moved up the hierarchy into the newly introduced ILoginEventBase base interface, which is shared with the new ILogoutCompletedEvent interfaces. This changes are source compatible, but as they are binary incompatible, a rebuild is required.

• In Telerik.Sitefinity.DynamicModules.DynamicModuleManager:
  • GetChildItemsHierarchy(DynamicContent item, Type childType = null) is changed to GetChildItemsHierarchy(DynamicContent item, IEnumerable childTypes = null). The method now accepts a list of child types instead of a single child type as parameter.
  • IQueryable GetChildItems(DynamicContent item, Type childType = null) method now returns query with child items of all statuses. Previously it returned child items with live status if the parent item is live and master otherwise.
• Telerik.Sitefinity.Descriptors.RelatedDataPropertyDescriptor: IContentLinksManagerProxy GetManager() method is removed since it was not used anywhere. Use ContentLinksManager.GetManager() instead.
• Telerik.Sitefinity.DynamicModules.Builder.Web.Services.IContentTypeService: In SaveContentType and SaveContentTypeInXml endpoints, parameter bool removeToolboxItem is removed.

changes - all execute code activities with deletion logic were changed to use the already built in Sitefinity CMS delete decision activity for one and two levels of approval workflows.

• Changes in the serialization of controller's properties:
  With the current release the actual type of the properties of a Controller is retained during serialization. Prior to this change, the properties of a controller were always serialized as a string. This change is part of the effort for the alignment of the functionality available for WebForms and MVC, since the data is serialized with keeping the actual type of a property for web forms widgets and the same notation for MVC widgets is kept. This way, it is easier to port designers from one widget to another or reuse code with both approaches.
• Ability to specify whether a MVC controller should be associated with certain <form> tag:
  New overloads of the Html.BeginFormSitefinity helper method introduce the ability to specify whether the controller should be associated with the generated form tag. The controller is associated with a tag by appending the controller Id to the query string of the form action URL. This functionality is useful in case there exist two different MVC widgets that have action methods with the same signature, the two MVC widgets are placed on the same page and you would like to invoke only the action of one of the widgets. Prior to the current change, the Html.BeginFormSitefinity helper method had always associated the controller with the generated tag. With the current release of Sitefinity CMS, the Html.BeginFormSitefinity helper method does not associate the controller with the tag by default anymore and instead, you should use the newly introduced overloads of the helper method.