Posted on 26. October 2013

Manage your SDK assemblies the easy way

NuGet has become the de-facto way of managing assembly references from within Visual Studio. Using the Package Manager you can easily download, install, update and uninstall referenced libraries automatically from the ever growing NuGet library repository.

In the past there was an unofficial package, but with the release of CRM2013, the SDK team have made the official assemblies available on NuGet. You can install the references to the CRM2013 SDK assemblies by Right Clicking on your Project from within Visual Studio and selecting Manage NuGet Packages…

If you search for Microsoft.CrmSdk in the Online tab, you will see a list of the official SDK assemblies.

Here are 5 really great things about using NuGet:

  1. All referenced assemblies are stored in a single solution folder named packages so that each project will reference the same assembly version inside your solution.
  2. You can update to the latest version using the 'Updates' tab inside the NuGet Package manager (or a specific version using the command line package manager).
  3. Any dependency assembly packages (e.g. IdentityModel) will automatically be downloaded and referenced in your solution
  4. You don't need to commit your dependency packages to Source Control. If you commit only your code to source control and then try and build the project on a new environment, you can easily re-download the assemblies from within the Package Manager using the 'Restore' button.


    If you want to automatically restore these files on build – you can Right Click on your solution and selecting 'Enable NuGet Package Restore'.

    See the article on the NuGet site for more information.
  5. You can use either the package manager to discover and install your packages, or use the NuGet Console to quickly install/uninstall if you know what you're looking for (Tools-> Library Package Manager - >Package Manager Console)

The package inter-dependencies with their names as referenced in NuGet are as follows:

You can see all of them listed at https://www.nuget.org/profiles/crmsdk/

Using the Package Manager Console you could install the latest Core Assemblies for CRM2013 using:

Install-Package Microsoft.CrmSdk.CoreAssemblies

Or you could install the CRM 2011 version using:

Install-Package Microsoft.CrmSdk.CoreAssemblies -Version 5.0.17

If you wanted to install them you can use:

Uninstall-Package Microsoft.CrmSdk.CoreAssemblies

Start using NuGet if you are not already and you'll never look back!

@ScottDurow

Posted on 24. October 2013

Upgraded to Orion? Upgrade to Ribbon Workbench for CRM2013

If your Dynamics CRM Online instance has been upgraded to Orion (CRM2013) you will need to upgrade to the latest version of the Ribbon Workbench for CRM2013. Since the Ribbon Xml Schema has changed slightly with CRM2013, the old version will no longer work.

Upgrade Steps:

  1. Open Settings->Solutions.
  2. Locate the Ribbon Workbench solution and click 'Delete'
  3. Download and Import the Ribbon Workbench for CRM2013.
  4. Refresh your browser and navigate to Settings->Solutions where you will find the new Command Bar button:

Further reading:

  1. Ribbon 'XML' Workbench for Dynamics CRM 2013 with a silent 'XML'!
  2. 4 things you need to know about the Command Bar
  3. Restore a Button that has been removed from the CRM 2013 Command Bar

 

Posted on 18. October 2013

How to fix CRM2013 Application Bar hidden by Silverlight Web Resource

If you have any Silverlight Web Resources in your site map that are hosted by an HTML Web Resource, you may find that when you upgrade to CRM2013 and use the pull down Application Bar the Silverlight page is rendered on top of the navigation buttons so that they are obscured and hidden from the user.

It might look something like the following:-

To fix this you need to adjust the Windowless property in the Silverlight object:

<object data="data:application/x-silverlight-2," type="application/x-silverlight-2" width="100%" height="100%">
    <param name="Windowless" value="true" />

Other than this I've not had any issues with Silverlight in CRM2013 but there is now a nice phrase in the SDK that states:

"Microsoft Silverlight web resources remain supported in Microsoft Dynamics CRM 2013 and Microsoft Dynamics CRM Online for backwards compatibility. For components that will be able to be presented on all clients, we recommend using HTML web resources with HTML5 instead of Silverlight."

If you need to convert your Silverlight Web Resources to HTML 5 and JavaScript, you could check out www.SparkleXRM.com.

@ScottDurow