Answered by:
Unable to see my custom work flow activity in the assembly for plugin registraion tool (CRM 2013)

Question
-
We used to have a simple worlflow activity in CRM 2013 environment. I had to make some simple changes. So, I unregistered it through the plugin registration tool. I also bumped the major version to 2.0.0.0
[
assembly: AssemblyVersion("2.0.0.0")]
[
assembly: AssemblyFileVersion("2.0.0.0")]
But when I load the .dll file in the plugin registration tool I do not see the anything under the assembly
Thus - I am unable to register my custom work flow activity.
Can someone help me out please?
Thanks,
Hasibur Rahman
Tuesday, December 9, 2014 4:53 PM
Answers
-
If the assembly shows, but not the plugin, then it is probably a problem with the plugin class. Things to check are:
- The class is public
- It inherits from CodeActivity
- Check the version of the .Net framework you've built against. If you're registering in the sandbox, it should be .Net 4.0 platform update 3 or higher
- If you're using the updated plugin registration tool (the UI looks more like the Crm 2013 UI), then I think it requires that you've built against a certain version level of the Microsoft.xrm.sdk and Microsoft.xrm.workflow assemblies. So, make sure your assembly references the same version as the SDK from which the plugin registration tool comes. Or you could try the plugin registration tool from an earlier SDK version
Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk
- Marked as answer by Hasibur Rahman Thursday, December 11, 2014 7:03 AM
Wednesday, December 10, 2014 5:32 PMModerator -
Hi,
You can try to use earlier version of plugin registration tool. use CRM 2011 plugin registration tool.
Thanks!
Kalim Khan
- Marked as answer by Hasibur Rahman Thursday, December 11, 2014 7:02 AM
Thursday, December 11, 2014 5:41 AM -
Yeah - I ended up using 2011 plugin registration tool and that worked like a charm. Weird thing is 2013 works with plugin - so, I wonder if there is some kind of bug for WFA.
Anyways - thanks David and Kalim for your time and effort in providing me help to resolve my issue.
- Marked as answer by Hasibur Rahman Friday, March 18, 2016 4:25 PM
Thursday, December 11, 2014 7:06 AM -
Thanks for your reply David.
May be I should a bit more - the wfa is made using C# from visual studio 2012.
I just did the "unregister " using the plugin registration tool - would that be the same as uninstalling?
I only bumbed up the version because initially I was not seeing the plugin in the assembly. After making the version change - the plugin does not show up. I can see the assembly but - there is no plugin inside it.
I changes the name of the assembly as well (like you suggested) but nothing happens.
[
assembly: AssemblyTitle("wfaReGecodeServiceRequestsCases2")]
[
assembly: AssemblyDescription("")]
[
assembly: AssemblyConfiguration("")]
[
assembly: AssemblyCompany("")]
[
assembly: AssemblyProduct("wfaReGecodeServiceRequestsCases2")]
Could there be anything else?
- Marked as answer by Hasibur Rahman Friday, March 18, 2016 4:25 PM
Tuesday, December 9, 2014 7:30 PM -
Hello David - thanks again for your reply
# I am using the following dll as my references from the bin directory of the plugin registration tool (that is being used)
MS.CRM.SDK.Proxy
MS.XRM.Client
MS.XRM. SDK
MS.XRM. SDK. Workflow
# I am using VS 2012 with .net 4.5
# Here is my code where I believe I am using everything that is required
namespace wfaReGecodeServiceRequestsCases
{
using System;
using System.Activities;
using Microsoft.Xrm.Sdk;
using Microsoft.Xrm.Sdk.Client;
using Microsoft.Xrm.Sdk.Workflow;
using System.Linq;
using Microsoft.Xrm.Sdk.Query;
using System.ServiceModel;public class ReGeocodeServiceRequestCases : CodeActivity
{
// Define Input Arguments
[RequiredArgument]
[Input("AddressLatitude")]
public InArgument<string> AddressLatitude { get; set; }[RequiredArgument]
[Input("AddressLongitude")]
public InArgument<string> AddressLongitude { get; set; }/// <summary>
/// Executes the workflow activity.
/// </summary>
/// <param name="executionContext">The execution context.</param>
protected override void Execute(CodeActivityContext executionContext)
{
// There are code here that compiles without error
}
}
}Could there be anything else
- Marked as answer by Hasibur Rahman Friday, March 18, 2016 4:25 PM
Wednesday, December 10, 2014 9:02 PM
All replies
-
Did you uninstall the plugin assembly, or just the types within it ?
Crm doesn't always cope well with changing an attribute of an assembly that impacts the strong name (such as the assembly version) if you don't also change the assembly name. I'd suggest either:
- If you hadn't previously removed the plugin assembly, remove it, and try again
- Change the assembly version back to the original version
- Or change the assembly name to a different name
Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk
Tuesday, December 9, 2014 5:43 PMModerator -
Thanks for your reply David.
May be I should a bit more - the wfa is made using C# from visual studio 2012.
I just did the "unregister " using the plugin registration tool - would that be the same as uninstalling?
I only bumbed up the version because initially I was not seeing the plugin in the assembly. After making the version change - the plugin does not show up. I can see the assembly but - there is no plugin inside it.
I changes the name of the assembly as well (like you suggested) but nothing happens.
[
assembly: AssemblyTitle("wfaReGecodeServiceRequestsCases2")]
[
assembly: AssemblyDescription("")]
[
assembly: AssemblyConfiguration("")]
[
assembly: AssemblyCompany("")]
[
assembly: AssemblyProduct("wfaReGecodeServiceRequestsCases2")]
Could there be anything else?
- Marked as answer by Hasibur Rahman Friday, March 18, 2016 4:25 PM
Tuesday, December 9, 2014 7:30 PM -
If the assembly shows, but not the plugin, then it is probably a problem with the plugin class. Things to check are:
- The class is public
- It inherits from CodeActivity
- Check the version of the .Net framework you've built against. If you're registering in the sandbox, it should be .Net 4.0 platform update 3 or higher
- If you're using the updated plugin registration tool (the UI looks more like the Crm 2013 UI), then I think it requires that you've built against a certain version level of the Microsoft.xrm.sdk and Microsoft.xrm.workflow assemblies. So, make sure your assembly references the same version as the SDK from which the plugin registration tool comes. Or you could try the plugin registration tool from an earlier SDK version
Microsoft CRM MVP - http://mscrmuk.blogspot.com/ http://www.excitation.co.uk
- Marked as answer by Hasibur Rahman Thursday, December 11, 2014 7:03 AM
Wednesday, December 10, 2014 5:32 PMModerator -
Hello David - thanks again for your reply
# I am using the following dll as my references from the bin directory of the plugin registration tool (that is being used)
MS.CRM.SDK.Proxy
MS.XRM.Client
MS.XRM. SDK
MS.XRM. SDK. Workflow
# I am using VS 2012 with .net 4.5
# Here is my code where I believe I am using everything that is required
namespace wfaReGecodeServiceRequestsCases
{
using System;
using System.Activities;
using Microsoft.Xrm.Sdk;
using Microsoft.Xrm.Sdk.Client;
using Microsoft.Xrm.Sdk.Workflow;
using System.Linq;
using Microsoft.Xrm.Sdk.Query;
using System.ServiceModel;public class ReGeocodeServiceRequestCases : CodeActivity
{
// Define Input Arguments
[RequiredArgument]
[Input("AddressLatitude")]
public InArgument<string> AddressLatitude { get; set; }[RequiredArgument]
[Input("AddressLongitude")]
public InArgument<string> AddressLongitude { get; set; }/// <summary>
/// Executes the workflow activity.
/// </summary>
/// <param name="executionContext">The execution context.</param>
protected override void Execute(CodeActivityContext executionContext)
{
// There are code here that compiles without error
}
}
}Could there be anything else
- Marked as answer by Hasibur Rahman Friday, March 18, 2016 4:25 PM
Wednesday, December 10, 2014 9:02 PM -
Hi,
You can try to use earlier version of plugin registration tool. use CRM 2011 plugin registration tool.
Thanks!
Kalim Khan
- Marked as answer by Hasibur Rahman Thursday, December 11, 2014 7:02 AM
Thursday, December 11, 2014 5:41 AM -
Yeah - I ended up using 2011 plugin registration tool and that worked like a charm. Weird thing is 2013 works with plugin - so, I wonder if there is some kind of bug for WFA.
Anyways - thanks David and Kalim for your time and effort in providing me help to resolve my issue.
- Marked as answer by Hasibur Rahman Friday, March 18, 2016 4:25 PM
Thursday, December 11, 2014 7:06 AM