We've been busy the last couple of months integrating SplendidCRM with Great Plains Accounting, but we took some time out to update the Web1.4 tree.
We started the Web1.4 node many months ago to take advantage of some of the major advances in .NET 2.0, such as MasterPages, Themes, WebParts and AJAX. Most of the MasterPages and Themes work was completed a few months ago and needed just a little more work to get the menus to function properly.
Using the new ASP.NET AJAX framework, formerly Atlas, was a breeze. I just a couple of days, we were able to add AJAX features to the charts on the Dashboard and to the Report editor. Feel free to make suggestions in our Features Forum as to areas that you would like to see AJAXified.
We are also making progress with WebParts. We have migrated all pages to use WebParts to manage the left Sidebar, and we have migrated the entire home page to WebParts. This will give SplendidCRM the same kind of functionality as SugarCRM's Dashlets. We still have to create the personalization provider to connect the WebParts user profile to SplendidCRM. For now, we are just letting it use the aspnetdb database.
Here are some of the Web.config changes that are necessary to support Web1.4
<
connectionStrings>
<add name="aspnetdb" connectionString="data source=(local);user id=iusr;password=splendidcrm2005;initial catalog=aspnetdb;"/>
</connectionStrings>
<httpHandlers>
<add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
<remove verb="*" path="*.asmx"/>
<add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
<add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" validate="false"/>
</httpHandlers>
<webParts>
<personalization defaultProvider="SqlPersonalizationProvider">
<providers>
<add name="SqlPersonalizationProvider" type="System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider" connectionStringName="aspnetdb" applicationName="/" />
</providers>
</personalization>
</webParts>
