I have to prepare the project for crm 2011's Update RollUp 18. From what I understand, from now onward the Micrososft.CRM.SDK dll is not supported anymore, thus I have removed it from my project. As one would expect, a lot of "could not be found" errors appeared because of the removal. For the code bellow, I have ".. Property could not be found.." and "..StringProperty could not be found .." .
public class ExtMergeName : ExtPropertyBase, ICrmString
{
public Property GetValue()
{
return CrmStringObject;
}
public StringProperty CrmStringObject
{
get
{
return (StringProperty)ReturnStringProperty();
}
}
What can I replace them with?
You are showing a snippet of Dynamics CRM 4.0 code. This is supported in Dynamics CRM 2011, up to the most recent Rollup Update. Support for CRM 4.0 is removed in Dynamics CRM 2013.
When your goal is to upgrade to CRM 2011 only, you can keep your VS projects as is, i.e. referencing assembly microsoft.crm.sdk.dll.
When you are planning to continue upgrading to CRM 2013 or CRM 2015, you need to rewrite your CRM 4.0 code. (Plugins, workflow activities, Javascript, external components accessing the CRM end points.)
More information about the programming model of Dynamics CRM 2011 and how to upgrade from CRM 4.0 can be found on MSDN:
Introduction to Programming Models for Microsoft Dynamics CRM
Summary of Changes Between Versions
In CRM 2011 and newer versions the microsoft.crm.sdk.proxy.dll is used, along with microsoft.xrm.sdk.dll. If you're not already using proper version of the CRM 2011 SDK, you can get that here: http://www.microsoft.com/en-us/download/details.aspx?id=24004. If you're trying to use the strongly typed entity classes in custom code, you can generate a correct version of that using the crmsvcutil.exe that comes with the SDK. If that's not exactly what you're looking for, then please provide additional details so I can better understand what you're trying to do.
Related
Is TFS 2015 is compatible with SharePoint 2016? Google search shows it is not compatible but didn't find any updated reference.
It's probably not compatible. The TFS integration with sharepoint is, at this point, more or less abandoned in favor of more flexible built-in dashboards, graphing, and reporting capabilities. You can still use Sharepoint for document management without having it explicitly integrated with an instance of TFS. I always recommend examining what you're using Sharepoint for in the context of TFS. I think you'll find that it's unnecessary to have it integrated.
Feels like I've been running in circles but how do I found that out? What lead me to cause was trying to install a plugin from IOTAP but the import failed.
'PluginType' entity doesn't contain attribute with Name =
'customworkflowactivityinfo'.
Any way of checking the latest rollup for CRM. I'm using 2011 that was an upgrade from 4 and it's online.
You can find an overview of Dynamics CRM version numbers on MSDN blog Dynamics CRM in the Field.
B.t.w. rollup 14 should fix your problem.
I'm developing a custom plugin for CRM. When I deploy plugin to CRM on Virtual PC, I get the error below.
Error registering plugins and/or workflows. Legacy plugin steps are
only supported in Pre-validation and Post-operation stages
How can I resolve this error ?
Like #Alex has said, it looks like you are using the CRM 4 sdk to develop your plugins. I would recommend using the CRM 2011 SDK in order to not have to rewrite your plugins once you upgrade to 2013 or above. Here's the link:
https://www.microsoft.com/en-us/download/details.aspx?id=24004
While upgrading a solution from CRM 2011 to CRM 2015, I only changed the header of solution.xml file generated in crm 2011 solution export zip to
<ImportExportXml version="7.0.0000.4013" SolutionPackageVersion="7.0" languagecode="1033"
generatedBy="CrmLive" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
and then I imported it to crm 2015. It got imported successfully.
Have any of you found any other way to import to crm 2015 from crm 2011 ?
Sometimes it will not be possible to import your solution this way, due to breaking changes in the solution file. In those cases you could follow these steps:
Import your solution in a clean CRM 2011 organization.
(If needed) upgrade your CRM deployment to the most recent rollup update for CRM 2011.
Upgrade your deployment to CRM 2013.
Upgrade your CRM deployment to the most recent rollup update for CRM 2013.
Upgrade your deployment to CRM 2015.
Export your solution.
Import your solution in your target CRM 2015 organization.
If the solution import does not complain about the validity of your solution, you should be safe to proceed. The import does its checks on the customization xml, so it can not damage your target organization.
In Dynamics CRM 2011 SDK the Xrm.Page Script Library template was at SDK\Templates\Xrm.PageScriptProjectTemplate location. But in CRM 2013 SDK no such location exists.
Also no such file campe up in folder search.
Do anybody have an idea about this?
I was the author of that template and chose to distribute it in the CRM SDK for CRM 2011. However, things got really busy and we just didn't have the bandwidth to maintain it. A third party solution: CRM Solution Manager (http://crmsolutionmanager.com) picked up the form scripting parts of it and added improvements along with many other useful capabilities. I would take a look at their solution if you found it helpful.
As far as I know the template has not been released for CRM 2013.
You can use the CRM 2011 one, but of course will not contains the new client methods introduced with CRM 2013.