What is Plugin using purpose Plugin writing Step

Plugin: -- A plug-in is custom business logic (code) that you can integrate with Microsoft Dynamics CRM 2011 and Microsoft Dynamics CRM Online to modify or augment the standard behavior of the platform. Another way to think about plug-ins is that they are handlers for events fired by Microsoft Dynamics CRM. You can subscribe, or register, a plug-in to a known set of events to have your code run when the event occurs.
Plugin tools Types: They are basically two types
A)     Preoperational  Plug-in (Asynchronous)
B)      Post operational plogin(Synchronous )

What is the purpose of plug in?
a.       Performing complex platform level data validation
b.      Performing auto-number generation
c.       Providing integration with other applications
d.      Executing complex business logic
e.      Data auditing and look up.
f.        Performing common database operations.

 syntax changes in Dynamics CRM 2011 plugins

1. The IPlugin now resides in Microsoft.Xrm.Sdk namespace instead of Microsoft.Crm.Sdk
public classClassName : Microsoft.Crm.Sdk.IPlugin
publicclassClassName : Microsoft.Xrm.Sdk.IPlugin

2. The Execute method signature of the IPlugin interface has changed; it now expects an IServiceProvider
instead of the IPluginExecutionContext.
publicvoid Execute(IPluginExecutionContext context)
publicvoid Execute(IServiceProviderserviceProvider)
3. To get a reference to the IPluginExecutionContext you now need to call the GetService method of the
IServiceProvider interface.
publicvoid Execute(IPluginExecutionContext context)
Microsoft.Xrm.Sdk.IPluginExecutionContext context =
(Microsoft.Xrm.Sdk.IPluginExecutionContext)
serviceProvider.GetService(typeof(Microsoft.Xrm.Sdk.IPluginExecutionContext));
4. ICrmService has been changed to IOrganizationService.
ICrmServicesdk = context.CreateCrmService(true);
IOrganizationServiceFactory factory = (IOrganizationServiceFactory)
serviceProvider.GetService(typeof(IOrganizationServiceFactory));
IOrganizationServicesdk = factory.CreateOrganizationService(context.UserId);
5. DynamicEntity has been changed to Entity.
·Properties property of DynamicEntity no longer exists
·Getting and Setting values no longer use *Property classes,
eg: no more KeyProperty, StringProperty…etc, simply do int value = (int)entity[“schema_name”];
if (context.InputParameters.Properties.Contains("Target") &&
context.InputParameters.Properties["Target"] isDynamicEntity)
if (context.InputParameters.Contains("Target") &&
context.InputParameters["Target"] isEntity)

Comments

Post a Comment

Hi,

If any one want to give the stagnation and change its most welcome.

Thanks!!
Rajesh Singh.

Popular posts from this blog

Many to Many Relationship in Dynamics CRM 2011.

Image
I get asked about many-to-many (a.k.a. N:N) relationships more than just about any other single topic, so here’s a summary of how they work in Dynamics CRM 2011. I’ll review both “native” and “manual” N:N’s, using a simple Association to Contact relationship to illustrate. This is a classic many-to-many: each association should be able to have multiple contacts associated with it, and each contact should in turn be able to be associated with many associations. Native N:N Relationships With native N:N relationships, you open up an entity for customization, click the N:N relationships link, and click the  New Many to Many Relationship  button and select the entity to create the relationship to. For the Association to Contact N:N relationship, I’ll start from the Association entity: In the previous figure, notice that Do no Display is selected in the Display Option for each side. I only show that to illustrate a point: what this will do is prevent the relationship from being displ
Read more

When to use plug-ins vs. workflow?

As a developer who is interested in extending or customizing Microsoft Dynamics CRM, you can choose from several methods to perform your tasks. In addition to adding client-side JavaScript code to a form or adding custom ASP.NET pages, you can write a plug-in or create a custom workflow by using the web interface that calls a custom workflow activity. How do you decide when to use a plug-in and when to use a workflow? The technology that you use depends on the task that you have to perform and who will author the customization. For example, you must use a synchronous plug-in real-time workflow if you want to execute custom code immediately before or after the core platform operation executes and before the result of the operation is returned from the platform. You cannot use an asynchronous workflow or asynchronous plug-in in this situation because they are queued to execute after the core operation finishes executing. Therefore, you cannot predict when they will run. If you wan
Read more

Create a Custom Workflow Activity...

Image
Required Software and Assemblies To develop Windows Workflow Foundation 4 custom activities, you must develop them on Microsoft .NET Framework 4. If you plan to register your custom workflow activities with Microsoft Dynamics CRM Online, you must build them using the Microsoft .NET Framework 4  PU3  (platform update 3) or a later version, such as .NET 4.5. The following assemblies must be added as references in your project. They can be found in the  SDK\Bin  folder in Microsoft Dynamics CRM SDK. Microsoft.Xrm.Sdk.dll Microsoft.Xrm.Sdk.Workflow.dll Use the CodeActivity Workflow Base Class To create a custom workflow activity, create a class that inherits from the  CodeActivity  workflow base class. This class is available in the  System.Activities namespace. Activities that inherit from the  CodeActivity  class can override the  Execute  method to produce custom functionality. To create a custom activity that inherits from CodeActivity Start Microsoft Visual Stud
Read more