locked
CRM 2013, VS 2010 and DeveloperToolKit RRS feed

  • Question

  • С Б.П.

    Hello everybody. 

    I have a problem with DeveloperToolKit for CRM 2013 and VS 2010

    I've downloaded SDK for CRM 2013, installed VS 2010 professional, SP1 for VS

    installed sdk\Tools\DeveloperToolkit\CrmDeveloperTools_Installer.msi

    Open VS, New Project - Microsoft CRM => New Visual Studio Solution
    Template For Dynamics CRM 2013 => OK
    => and got an error :

    ---------------------------
    Microsoft Visual
    Studio
    ---------------------------
    Error: this template attempted to load
    component assembly 'Microsoft.CrmDeveloperTools, Version=1.2.0.0,
    Culture=neutral, PublicKeyToken=31bf3856ad364e35'. For more information on this
    problem and how to enable this template, please see documentation on Customizing
    Project Templates.
    ---------------------------
    OK  

    ---------------------------

    I've checked on another computer also with VS 2010 - the same error

    Installed DeveloperToolKit for CRM 2011- everything works fine, without errors

     Any suggestions?

    Tuesday, October 8, 2013 9:41 AM

All replies

  • I am experiencing the same problem. Did you ever find a way to resolve this? I see that your original post is 2+ weeks ago.

    If I start Visual Studio up with logging I can see repeated, failed attempts to load the package in the Activity Monitor Log

    CreateInstance failed for package
    [Microsoft.CrmDeveloperTools.CRMDeveloperToolsPackage,
    Microsoft.CrmDeveloperTools, Version=1.2.0.0, Culture=neutral,
    PublicKeyToken=31bf3856ad364e35]

    • Edited by Chris Grubb Friday, October 25, 2013 6:46 AM Additional detail
    Friday, October 25, 2013 6:44 AM
  • It is  a bug with VS2010 version. I have reported to MS via Connect. They mentioned that it is fixed and will be available in the next SDK drop. Meanwhile, I downloaded the VS2012 trial edition (good for 90 days) to work while waiting to the release

    Friday, October 25, 2013 6:49 AM
  • Just in case you have not download yet, the fixes is ready in the new SDK here http://www.microsoft.com/en-us/download/details.aspx?id=40321. Tested and the error is gone now
    Saturday, November 2, 2013 3:34 AM