read more..
We had a requirement today to run a DotNetNuke Website in .Net 4.0 as some code we are using as part of the Microsoft CRM 2011 SDK require .Net 4.0.
Problem is that with many of the DotNetNuke websites, they have some references that will cause this error when you flip your website worker process to 4.0. in IIS.
This will give you an error that looks like this:
Generates an error:
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately. Compiler Error Message: CS1703: An assembly with the same identity ‘System.Web.Extensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35′ has already been imported. Try removing one of the duplicate references. Source Error:
[No relevant source lines]
Source File: Line: 0
Show Detailed Compiler Output:
Interestingly too the reference to Version=4.0.0.0 initially said Version-3.5.0.0 until the second page refresh on the error.
The problem in our case, and it may differ with others, related to an older file for Microsoft Ajax.
There is a file called: System.Web.Extensions.dll
in the \bin folder.
We renamed this to: System.Web.Extensions.dll.bak
And our problem was fixed.
This is due to an older way that Microsoft handled Ajax vs the new way in .Net 4.0.
We do offer DotNetNuke support services and would be happy to assist others with this or other DNN problems that need professional support services with.
http://www.interactivewebs.com/Services/DotNetNukeSupport.aspx
During an update from DNN 4.9.5 to DNN 6x we experienced:
All pages with HTML blank when logged out, but show this error logged in.
Error: Services is currently unavailable.DotNetNuke.Services.Exceptions.ModuleLoadException: The type initializer for ‘DotNetNuke.Modules.Html.DataProvider’ threw an exception. —> System.TypeInitializationException: The type initializer for ‘DotNetNuke.Modules.Html.DataProvider’ threw an exception. —> System.InvalidCastException: Unable to cast object of type ‘DotNetNuke.Modules.HTML.SqlDataProvider’ to type ‘DotNetNuke.Modules.Html.DataProvider’. at DotNetNuke.Modules.Html.DataProvider.CreateProvider() — End of inner exception stack trace — at DotNetNuke.Modules.Html.WorkflowStateController.GetWorkflows(Int32 PortalID) at DotNetNuke.Modules.Html.HtmlTextController.GetWorkflow(Int32 ModuleId, Int32 TabId, Int32 PortalId) at DotNetNuke.Modules.Html.HtmlModule.OnInit(EventArgs e) — End of inner exception stack trace —
In our case, the upgrade left 2 things behind that DNN 6 did not like.
Save and you are done.
Specifically we wanted to take a version of DotNetNuke from 4.9.1 to 6.1.3 today and actually found that it worked perfectly.
We did take some steps that helped a lot. This may be of value to some of you.
1. Backed up the entire file system for the website.
2. Backed up the database on SQL server for the site in question.
3. Ensured we had a HOST login account that worked.
4. Ensured the server we were running on (Windows 2008 R2) was patched and running .Net Framework version 3.5 SP1.
5. If your site is busy, work out a way to stop the traffic. One way is to add a portal alias, like test.domain.com in your DNN website. Setup a DNS entry to that test.domain.com points to the IP address of your DNN web server. In IIS, setup a Binding, so that test.domain.com will answer for your site.
Then access the site on test.domain.com and check you can login, etc.
Then remove the binding in IIS for www.domain.com (temporarily while you play upgrade).
This way, the site will not answer normal user access, but will answer you when you go to test.domain.com.
We suggest the following table for upgrading your DNN Website.
Note: If you are upgrading a version prior to DNN 4.6.2, then you will need to manually update the web.config file. After this version the updates are automatic.
On Codeplex, Click on View All Downloads
Find the version for the next upgrade step from the table above. Then find the Version Upgrade download link.
Download the .zip file to your server. Then extract the contents directly over the existing website directory structure.
You will be asked to overwrite files, Tick yes to all.
You will be asked to overwrite folders, Tick Apply to all – And continue.
Once you have extracted, hit your website in a browser, and watch the upgrade happen before your eyes.
Repeat the steps of backing up after each successful update, and download the next update package and repeat the process.
If you are using the XML module, on a DNN version before 5.3.0, then you should obtain the latest update of the module before moving past 5.3.0.
If you have the Ifinity URL Master module. We suggest turning it off to upgrade.
In IIS you will wan to move the website to a new application pool that is running .net 3.5 or 4.0 Integrated. You cannot share application pools with earlier DNN versions that run on .net 2.0.
Jump into the HOST settings, and configure things like, friendly URL’s, DNN Host Menu Options, and performance settings.
If you disabled bindings (from the initial steps 5 above) re-enable them and test access.
We offer a DotNetNuke Support Service that can include the upgrading of DNN websites for you. This is especially useful if you are not confident with either .net websites or IIS server administration.
We are happy to help you evaluate the upgrade path and potential problems. The cost of the service is in effect calculated at at an hourly estimate. It should be noted that if everything goes well, and trouble free, there there is at least 1 hours work in this upgrade, usually more as there are often little bugs to sort out.
Please contact us for support here: http://www.interactivewebs.com/Services/DotNetNukeSupport.aspx
http://www.datasprings.com/resources/articles-information/dotnetnuke-articles/upgrading-dotnetnuke-4.9-to-dotnetnuke-6.0
today we are please to announce that the advanced login module for DotNetNuke includes the utilisation of the single sign-on feature that has previously only been available to the Professional Edition since DotNetNuke 6.1.
Now it is possible to add this feature to your website with one simple module, that as the feature throughout your entire website and child websites on a single DotNetNuke instance.
The idea is that you create a site group, specifying the master site and included child sites. Once the configuration has been created, a user will be able to login to either the Master site or any of the specified child sites within the group using the username and password details from the master sites user database.
We have included this feature within the advanced login module, and it works with the community edition. The feature can be found on the tab called site groups:
This is a descriptive field only and is used to distinguish one site group from another. You can put anything you like in this field that will help you remember the details of the site review are creating.
This is an additional descriptive field that allows you to put text that helps you explain the meaning behind the creation of the site group you are creating. This is a reference field only and can contain any descriptive text.
The master site is the primary site that contains the user names and passwords that you wish to use to sign on to either the Master site or the child portals. It is vital that you select the correct portal to use as the Master site.
An example:
InteractiveWebs is a DotNetNuke website that has one master portal that we used to run the interactive webs website on, and dozens of child portals. Each child portal is used to represent one of the modules that we have created the DotNetNuke. There are lots of them.
When users register on the interactive webs website they are registering on our primary portal. When users visit the child portals information on a module or other service that we provide we do not encourage them to register as users on his child portals. As a matter of fact we had previously redirected the login buttons back to the primary portal so that anybody wishing to register or login is always directed back to the primary portal. This means we have an extensive user database on our primary portal.
So in this example we would definitely need to select the interactive webs primary portal as the master site as it is this site that has all of the thousands of usernames and passwords that we wish to use across all of our child portals.
The authentication domain is the domain name that is used primarily across all of the portals that the site group is using. In the case of interactive webs, we have utilised a conical redirection within the site alias settings to ensure that users of our portal remain on the same domain: interactivewebs.com even though we have multiple domain names pointing to the website.
For more information: http://www.interactivewebs.com/advancedlogin
We were receiving some really really strange behaviour with a dotnetnuke website.
The log files showed:
Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid. with EVENT ID 1315
Login with Internet Explorer worked.
Login with some versions of firefox failed others worked
Login with Chrome failed.
When login failed, the browser would refresh and then show the page you were on before login.
Now in this instance we tried nearly everything we could think of. we tried different application pools different.net settings in IIS. and we hand we have a good idea of both server management and asp.net.
He also had is particularly confused that other DotNetNuke websites on this particular server were running just fine.
To cut a long story short the problem turned out to be very specific that site we were using.
We were in the process of migrating somebody else’s site to our servers, and we had exported their site and site content using the DotNetNuke template feature. Ordinarily this would work just fine, however in this case the user on the other website had defined the login.aspx page to have administrator only privileges. They had set the login link from the skin to automatically directed to the login.aspx webpage. In the site settings they had defined no page for the DotNetNuke login page.
What this meant was that as the user attempted login to the DotNetNuke website, the attempt to call the login.aspx page was made and the DotNetNuke automatic lockout protection system was called in to play. This lockout protection system will throw up the standard DotNetNuke login screen, if the page is either undefined or unavailable as with both the case with this website. It just so happens that this lockout protection system doesn’t work particularly well with chrome. That’s a whole not a problem and I don’t intend to solve.
The solution here was to login using Internet Explorer, enable permissions on the login.aspx page which in the DotNetNuke website was simply called login. I was then able to select this page as the login page in the admin/site settings page. Once the login page was correctly defined I then ensured that the login module that come standard with DotNetNuke was included on this page.
After making these changes to the settings, we stopped receiving the error message:
DotNetNuke Event message: Forms authentication failed for the request. Reason: The ticket supplied was invalid. EventID 1315
And the site continued to operate correctly from there. Now whilst this was a very particular configuration that was imported from an invalid template website. I have noticed that in forums discussing this event ID, nobody has come up with a solution suggesting to look for the validity of your login settings within DotNetNuke. Hence the reason for this blog post.
I hope that saves somebody a lot of time, as I blew nearly 2 days try to resolve this one.
If anybody needs assistance with this type of problem, please feel free to contact us on our website.
Recently there was an update to jQuery that caused some problems with DotNetNuke. The problems include:
The problem is associated with some bugs in the jQuery released and hosted googleapis. The bugs are not related to DotNetNuke directly but the jQuery used in many instances of jQuery.
The solution is an easy one. You just need to login to your DotNetNuke website with a Host Account, and modify the jQuery settings under the HOST / ADVANCED SETTINGS to a more recent and bug free version of jQuery UI.
Pasting this URL: https://ajax.googleapis.com/ajax/libs/jqueryui/1.8.23/jquery-ui.min.js into the “Hosted jQuery UI URL" and ensuring the “Use Hosted jQuery Version” is ticked.
Recently while working with a DotNetNuke website, we found that attempting to login to the site generated this error:
SQL Exception Error Details File Error Index #: 0 Source: .Net SqlClient Data Provider Class: 17 Number: 1105 Procedure: AddEventLog Message: System.Data.SqlClient.SqlException: Could not allocate space for object ‘dbo.EventLog’.'PK_EventLogMaster’ in database ‘www.sitedatabase.com’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteNonQuery(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.SqlDataProvider.AddLog(String logGUID, String logTypeKey, Int32 logUserID, String logUserName, Int32 logPortalID, String logPortalName, DateTime logCreateDate, String logServerName, String logProperties, Int32 logConfigID) at DotNetNuke.Services.Log.EventLog.DBLoggingProvider.DBLoggingProvider.WriteLog(LogQueueItem logQueueItem)
After a investigating the site and server we found that this was caused by the SQL server running out of room on the disk hosting the database connected to this DNN site.
Free up more space on the SQL database disk.
When you get a black background in the HTML Editor.
The solution is easy.
Look for the file found here:
\Providers\HtmlEditorProviders\Telerik\Config\ConfigDefault.xml
Edit it to add this line:
<property name="CssFiles">~/Providers/HtmlEditorProviders/Telerik/Config/EditorCustom.css</property>
Looking like this:
Then edit this file:
\Providers\HtmlEditorProviders\Telerik\Config\EditorCustom.css
To look like this:
body { background-color: white; background-image: url(image_path); color: black; }
That’s about it.
After upgrading a DNN website, we received this error message.
The underlying cause of the problem is sloppy release version upgrades of the DNN core product.
The issue is that the release.config file in the update versions of DNN references older versions of the Telerik.Web.UI .dll file in the /bin folder of the install versions of DNN. This means that the settings in your newly updated web.config file are referencing an old version of the Telerik file.
The fix is easy
Right click on the Telerik.Web.UI.dll file in your sites /bin folder.
If the file is not there, then download the install version of your DNN site package from http://dotnetnuke.codeplex.com
Then extract the file to the /bin folder.
Look at the version number of the file.
Edit your web.config file to match this data:
If you are trying to upgrade your DotNetNuke site and found that you are presented with the Welcome to the DotNetNuke Upgrade Page, but can’t login with your Host (SuperUser) account.
Welcome to the DotNetNuke Upgrade Page.
The first step is to choose the language you wish to use for the Upgrade.
You are about to upgrade your website to a more recent version of the DotNetNuke application. Applying upgrades on a consistent basis is the best way to ensure that you are protecting the integrity of your investment and the security of your users and assets. Before proceeding with the automated upgrade process please ensure that:
Just simply close your browsers, or better yet, grab a browser that you have not accessed for some time. Then try hitting your URL and loggin in with the new browser session. While I did not bother to work out what the cache issue was, I did find it was cache related to an open browser session that was trying to authenticate to a previous session.
Easy when you know how~!
It is technically possible to remove templates or login tokens from the module and lock yourself out of the website. The module has protection from this event in two ways.
If the module detects that you are updating the module settings and have totally removed the templates, it will detect this state and use a default template when accessing the front end of the module.
Additionally if you were to access your login page with this module on, and found that you do not have any buttons to press for access, you can revert to a login protection mode by adding some text to the URL. This will force the module to display some basic login details.
Just add: “?loaddefault=true” (without the “”) to the URL with the module on it. So as an example if you have the module on the home page you would use:
· http://www.domain.com/Default.aspx?loaddefault=true
This will load the default template shown above.
This ensures that the Advanced Login module for DotNetNuke will not lock you out of your site and prevent you from logging in.
http://www.zendesk.com/ Zendesk is an online ticketing system designed to manage support tickets through a website interface. Zendesk is one of the more popular ticketing systems available as a software as a service.
We have included within the advanced login module the ability to login to Zendesk using your DotNetNuke user database. This makes it possible to manage all of your user support tickets for your DotNetNuke website within the Zendesk software as a service ticketing system, without having to have a separate database if users.
Configuration of this system is extremely easy. There are two settings required one is within the Zendesk interface, and naturally requires you to have signed up for services with Zendesk.
The other is within that advanced login module for DotNetNuke.
Zendesk allows you to configure a remake URL that is referenced logging in. There should be a URL on your website that has an instance of the advanced login module installed on the page. That instance of the module needs to be configured to work with Zendesk.
When a user clicks on the login button at Zendesk they are redirected to the URL mentioned above. They login to the DotNetNuke website with the normal advanced login interface of your choice. They will then be redirected back to the Zendesk helpdesk having been authenticated through your DotNetNuke user database.
Setup a page with the advanced login module installed. We recommend that you use the page that is the default login page the DotNetNuke. We have explained elsewhere in the manual how to configure this page with an admin only view of the normal all standard DotNetNuke login module, and included in instance of the advanced login module. You can then define in the administrator settings of your website to use this to find page as the login page for your website.
This does not prohibit you from using the advanced login module with more advanced modes like slide down or pop-up effect on other pages of your websites, but it does ensure that should anyone be directed to the normal login page DotNetNuke that they are presented with an instance of the advanced login module. This is the instance that will be used to configure the Zendesk settings.
Some of the great advantages of using DotNetNuke as your authentication provider for Zendesk, include the ability to integrate deeply your Zendesk ticketing system directly into your DotNetNuke website without having to cross over your user database.
Additional information is available from our website in the support page user manual.
http://www.interactivewebs.com/advancedlogin/DNNLoginModule.aspx
Recently DotNetNuke launched the ability to configure Google authentication for login to your DotNetNuke website. This feature made its debut in DNN 6.2
we have updated the advanced login module to include the ability to use a token to display login options for the Google authentication system that is available in DotNetNuke 6.2 .
The utilisation of the token requires you to preconfigure your DotNetNuke website with the Google authentication provider. A good description of how to do this is available here:
How to enable or disable the DotNetNuke Google authentication system that allows users to login to DNN using their existing Google account to login to DotNetNuke.
Prerequisites. You will need to sign up for a Google Authentication account to complete this tutorial. This authentication system must be enabled by a SuperUser (see "Managing Authentication Systems") before it can be viewed and configured.
8. Click the Update Authentication Settings link. The Google login button is now displayed on the Login page and any Account Login modules.
After you have correctly configured DotNetNuke to allow the Google authentication provider. You may use the new token within the advanced login module templating system.
The token is: [login_google_button]
Which simply places button on the login page indicating that the user can utilise the Google login system.
Nothing could be simpler.
Additional information about the DotNetNuke advanced login module please visit: http://www.interactivewebs.com/advancedlogin
During the installation of the DotNetNuke Microsoft pivot module, it is necessary to several changes to be made to the web.config file. These changes allow the Silverlight pivot technology to operate on the DotNetNuke website. We have automated the installation process to automatically update the web.config file during the installation of the module.
Please remove the following things under <system.web>
<add verb="*" path="*.cxml" type="iwebs.Modules.Pivot.CXMLHandler,App_SubCode_Pivot" validate="false"/> <add verb="*" path="*.jpg" type="iwebs.Modules.Pivot.TileHandler,App_SubCode_Pivot" validate="false"/> <add verb="*" path="*.dzc" type="iwebs.Modules.Pivot.DZCHandler,App_SubCode_Pivot" validate="false"/> <add verb="*" path="*userprofile.aspx" type="iwebs.Modules.Pivot.ProfileHandler,App_SubCode_Pivot" validate="false"/>
<add verb="*" path="*.cxml" type="iwebs.Modules.Pivot.CXMLHandler,App_SubCode_Pivot" validate="false"/>
<add verb="*" path="*.jpg" type="iwebs.Modules.Pivot.TileHandler,App_SubCode_Pivot" validate="false"/>
<add verb="*" path="*.dzc" type="iwebs.Modules.Pivot.DZCHandler,App_SubCode_Pivot" validate="false"/>
<add verb="*" path="*userprofile.aspx" type="iwebs.Modules.Pivot.ProfileHandler,App_SubCode_Pivot" validate="false"/>
Also the ones under </system.webServer>
<add name="CXMLHandler" verb="*" path="*.cxml" type="iwebs.Modules.Pivot.CXMLHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/> <add name="JPGHandler" verb="*" path="*.jpgx" type="iwebs.Modules.Pivot.TileHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/> <add name="DZCHandler" verb="*" path="*.dzc" type="iwebs.Modules.Pivot.DZCHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/> <add name="ProfileHandler" verb="*" path="*userprofile.aspx" type="iwebs.Modules.Pivot.ProfileHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/> <add name="TileHandler" verb="*" path="*_files/*/*_*" type="iwebs.Modules.Pivot.TileHandler,App_SubCode_Pivot" preCondition="integratedMode,runtimeVersionv2.0"/>
<add name="CXMLHandler" verb="*" path="*.cxml" type="iwebs.Modules.Pivot.CXMLHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/>
<add name="JPGHandler" verb="*" path="*.jpgx" type="iwebs.Modules.Pivot.TileHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/>
<add name="DZCHandler" verb="*" path="*.dzc" type="iwebs.Modules.Pivot.DZCHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/>
<add name="ProfileHandler" verb="*" path="*userprofile.aspx" type="iwebs.Modules.Pivot.ProfileHandler,App_SubCode_Pivot" validate="false" preCondition="integratedMode"/>
<add name="TileHandler" verb="*" path="*_files/*/*_*" type="iwebs.Modules.Pivot.TileHandler,App_SubCode_Pivot" preCondition="integratedMode,runtimeVersionv2.0"/>
We have often receive lots of questions about Web-safe fonts, or web friendly fonts. We have products that work with technologies like Microsoft Word, and publish back to websites like DotNetNuke. (DNN Word Editor)
The issue is that not all fonts will work on all browsers on all computers. Here is the reason why.
There are an awful lot of fonts in the world! For years, no doubt, you’ve been using a ton of them in word processing documents, party invitations, banners, etc. But have you ever noticed how few of them are used on the web?
There’s a really good reason for this. When a web page loads, the browser is told to write text onto the screen using a specified font—one that is stored on the computer that the browser is running on. Therefore, if the web page’s code is calling for a font that a user does not have installed on their computer, it won’t show up! What that person will instead see is a default font, which might look a little ugly.
Now you might be wondering why this will happen so often if there are so many fonts installed on your computer. Well, here’s the problem: the two most widely-used operating systems—Windows and Mac OS X—each come installed with a different set of fonts. Awesome!
To illustrate this point, here’s where the fonts are stored in Windows 7:
And here’s where they’re stored on Mac OS 10.6:
Right away, we can see that only one of the displayed fonts overlaps: Arial. None of the Calibri orCambria fonts are available on the Mac, and the Mac has at least a dozen just on this page that aren’t available in Windows!
In fact, between these two systems, there are only ten fonts that overlap:
Those fonts that fall into that middle area, covered by both operating systems, are what we callweb-safe fonts. If you use Calibri on your webpage, Mac users won’t see it; if you use Andale, Windows users won’t see it; but if you use Georgia, you can rest assured that users of both systems will see the it.
Now there’s a bit of grey area here. Users of older operating systems don’t have some of these fonts we’ve declared web-safe. For example, Windows XP users don’t have Palatino or Trebuchet MS. Even worse, users of Android mobile phones don’t have any of these fonts.
So to be clear, there are only five fonts that are considered universal:
Feel free to use these fonts all you want! Even if you dug up that old Packard Bell you had back in 1997 and it didn’t explode when connected to the modern web, you’d be able to see these fonts rendered as intended. Those Android users will just have to fight for themselves.
*The green marks show very common fonts, the yellow shows not so common but all are generally accepted as web safe.
Your text will still be visible, but the browser will use whatever default font it supplies for situations like this. This means that you may have intended to use a cute, scripty font, but what you get is
Your text typed in a regular serif font.
This is good because your content still goes through, but your design might be compromised. Therefore, you should always specify fallback fonts and a category that the font falls into. Let’s say that you want to use Helvetica, but you’ll settle for Arial. Since both of these fonts are considered to be sans-serif fonts, you can write a CSS declaration like this:
{ font-family: Helvetica, Arial, sans-serif; }
The browser will first try to use Helvetica, and if it’s not installed, it’ll attempt to use Arial. If even that font is not available, it’ll use whatever default sans-serif font the browser likes, but at least it’ll be the correct type of font!
For more information about coding fallbacks, alternative methods to using non-web-safe fonts, and everything typography related, you can pick up a copy of our Web Typography Handbook. It’ll tell you everything you need to know.
Today we announced that our DotNetNuke Module for syncing to outlook was updated to DNN 6. Check out the details here.
http://www.dotnetnuke.com/Resources/Forums/forumid/112/threadid/451288/scope/posts.aspx
I noticed a question today on a Microsoft Dynamics CRM discussion site asking
“is there anyone who is not trying to sell me their product, that has done something interesting with CRM and Silverlight?”
Well yes there is…
InteractiveWebs have done several interesting projects with Silverlight as an interface to Microsoft CRM.
One of the most interesting of these is a Silverlight membership login system for a grain trading company based in Australia. The business is an organisation that trades produce in a similar way to how shares are traded in the stock market. The difference being that the commodity being traded has been grown by “growers” (farmers) and represents the produce that their farm has for sale in the open grain trade market.
Interestingly, Microsoft CRM is being used entirely for the backend management of this trading. This is quite complex in it’s design as you can imagine would be the case if you were running a stock exchange using CRM.
Entities are being used to track the bidding for sales and purchasing of hundreds of different qualities of different grains, at different locations over an entire country.
Of note to the Silverlight interface, is the fact that there are an ever increasing number of records within this system in the order of 65,000,000 records of some CRM Entities.
In it’s simplest function, the Silverlight interface is a membership system.
Allowing users to login and manage the buying and selling of commodities. Very similar to how users of a Stockbroking system would login and buy and sell their shares. But of course the user data is all being driven from a CRM backend running CRM 2011 with IFD.
The membership login is using custom attributes within CRM Contacts to authenticate and allow login.
Once logged in the user can modify personal details that are saved back to the CRM Contact entity.
Data is retrieved live using XRM to interface with CRM on the fly. Silverlight gives a clean and robust interface for users.
Just like with the sale of share, there is some paperwork generated with the buying and selling of commodities. Broker Notes, Freight Invoices, and Monthly trade Statements are example of just a few. Originally the thought was to interface with a Microsoft SharePoint server to store the related .PDF documents generated for these items. Instead we took the simpler approach of attaching the .PDF documents to the relevant records in the custom entities that are used to track each trade.
This data is simply stored as CRM Notes with Attached Files (.pdf) to the custom Entities.
Then in the Silverlight interface we allow users to open (on the fly) these notes and attached .pdf files to view the “paperwork” associated with each sale.
Summary data is presented that is referencing custom attribute data, and able to be exported live from Silverlight to Excel.
Or clicking on the PDF icon, will open the associated attached note from CRM and open the .pdf record live.
Example of PDF data.
Growers of commodities can create new stock records, listing the gran they have, quality, quantity, location etc in a simple user interface.
Listing too the price they wish to achieve in order to sell the produce.
Doing this creates a new record in a custom Entity in CRM directly, and this data is used in the bidding and selling process.
The data is available to Silverlight users in their record of stock.
Similar in concept to a statement of shares for a stock market trader.
So far, these are reasonably simple interfaces using XRM to CRM. Reading, writing, opening attached files etc. Where it gets interesting is in some real time graphing that we do to show bids on stocks / commodities.
For this we are needing to access tens of thousands of records that represent different bids for different commodities and work out on the fly the best or highest bid, and show that to the client in a fast loading graph.
This is where Silverlight and some cleaver XRM calls to some cleaver processes in CRM delivers a great result.
With the great graphing tools in Silverlight, the graph draws in real time and animates the loading of data. It has a full screen mode:
And is really a great use of Silverlight for this particular task.
One of the features we built on this interface is the ability to “Run Out of Browser”. So the client can right click the interface and select to “Install to this computer”.
This adds the project to an Out of Browser Silverlight experience that can be launched as any other application or program from your computer.
This feature of Silverlight can run on a Mac or PC, and delivers an experience for end users that is very similar to having a membership program installed on your computer.
The project will auto update if we modify the web based source version with a new release automatically. The client is promoted with a messaging saying the program will close to update, then opens with the new version automatically. Truly using the best experience that Silverlight has to offer.
Uninstalling the out of browser app is as simple as a right click in the app, and selecting from a dropdown “Remove this application”.
Kind of like a windows 8 experience with any pc.
Silverlight… ahhh what to say about Silverlight….. where to start.
1. We drank the Kool Aid. Microsoft told us how great Silverlight would be, how it would segregate the design team from the development team and deliver the benefits of keeping people within their specializations.
2. We spend years of time investing in Silverlight development. We get it, we can work with it and we can do amazing things with it. This and other cool projects including a MS Pivot interface to DotNetNuke and Microsoft CRM data.
MS Pivot and CRM – http://demo.interactivewebs.com.au/dnnpivot/dnnpivot_demo.htm
3. We kicked it’s butt. We were able to deliver anything we wanted using Silverlight and made it interface with a multitude of data sources at multiple times using XRM and other web services to pull data from both CRM and other data sources.
We get it, we can do it, we hate it and we regret the time we wasted after Microsoft mislead us into their Silverlight sphere.
Microsoft Silverlight Evangelist – We drank the Kool Aid
Silverlight never came close to delivering on any of the promises that Microsoft made about it.
It is tricky to develop in, it is poorly supported by even Microsoft, design tools are definitely lacking greatly, the development experience was a mine field of poorly documents bugs and broken features that required time and commitment to untangle the crap that Microsoft produced.
It was amazing to us how many things we were doing and solving that literally no one else was talking about. We felt like the first team walking on the Silverlight moon at every step of the way.
The end result is something that we are proud of. There are some cool features that we think make the project example above shine. But for all the time, and trouble invested to deliver it, it is just not worth it!
If looking at this and other similar projects again, we would use other technology to more quickly develop a very similar experience. There quite simply is nothing in Silverlight in interfacing with CRM that we can do easier other ways.
So there you have it. A good example of Silverlight with CRM, and the reason why we would suggest you use other technology yourself.
And check out that Silverlight Pivot link above. It is actually very cool too in what it does and how it does it. We have rigged this to work against any internet facing CRM environment including the Microsoft Hosted CRM.
We wrote this to help someone asking for a non commercial plug for a Silverlight in CRM example. We hope the above meets the requirement of that… but we are a development and CRM business, so we need to mention that if you need some cleaver interfacing with CRM. Then please contact us here http://www.interactivewebs.com/ContactUs.aspx.
We have other examples to show too.
Recently we launched a new website called Network You. The site can be found at networkyou.org.
Of particular interest on the site is a new module or ours soon to be released to the DotNetNuke Community called Mushroom Video Module.
The module will feed Youtube Play Lists from youtube.com directly into your site in an easy to manage and easy to use video feed.
The end result of the feeds looks like this:
http://www.networkyou.org/Network/GlobalVillage.aspx
With the video feeds being selected directly from a play list selector button that referenced a YouTube account name.
The module also uses the template system developed by InteractiveWebs for the display system that allows simple to load templates to be customized to the users requirements.
An example of the module with multiple feeds onto a single page is this one: http://www.networkyou.org/Network/Professionals/VideoTopics.aspx
We will be releasing the module to the public in the next few weeks. We would love to hear any comments!
Steps to add an Attachment Field to Feedback Designer Module for DotNetNuke.
The result is a form with file upload ability. The attachment is sent as an email attachment.
Please contact us for additional DotNetNuke Support requirements.