Adxstudio Portals 7.0 contains a number of major enhancements to how Adxstudio Portals applications are installed and built.
Adxstudio Portals 7.0 introduces a new way to manage Adxstudio components and data in CRM. Instead of importing CRM solutions manually, as in previous versions, simply import the AdxstudioInstaller solution, then launch the solution configuration page.
From this interface, you can install and update the Adxstudio components you want, and have their dependencies installed automatically. The installer will also help you keep your installation up to date, and let you install additional solutions and data from the Adxstudio Community Gallery.
Adxstudio Installer is now the preferred way to manage Adxstudio components in CRM.
Built for Microsoft Dynamics® CRM 2013
Adxstudio Portals 7.0 is built for CRM 2013, to take advantage of the latest features of the platform.
Adxstudio Portals has been updated to use the latest version of the Bootstrap front-end framework, for improved responsive layout on mobile devices.
Adxstudio Portals Web Forms and Managed Forms have been updated to support attachments that are integrated with SharePoint.
Removal of Xrm.cs Code-generated File
We have rewritten the master portal to not have any dependency on the code-generated Xrm.cs file that we included in the project. Our portals now use late-bound context methods so that you no longer need to use the code generated file. In past versions, if you only imported some of the feature solution files that we ship and re-generated the Xrm.cs file, the portal would have thrown compile errors for features that you did not import and that would require you to exclude those files from your project file. The new master portal will now compile without any code-generated file. You are free to continue to use the early-bound context mechanisms and generate your own file, but the portal will not require it and will not give you compile errors for any missing features.
This also introduced a new Property control that works in this manner.
<adx:Property DataSourceID="CurrentEntity" PropertyName="adx_copy" EditType="html" runat="server" />
The control prefix was formerly crm and is now adx. The PropertyName value must also now be lowercase to represent the logical name of the attribute.
This also introduced a new Snippet control that works without the code-generated file.
<adx:Snippet SnippetName="Social Share Widget Code Page Bottom" EditType="text" DefaultText="" runat="server"/>
The control prefix was formerly
crm and is now