web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / CRM 2011 on-premises -...
Microsoft Dynamics CRM (Archived)

CRM 2011 on-premises - Developer Toolkit wrapper plug-in C# for VB .Net plug-ins

(0) ShareShare
ReportReport
Posted on by Ankit Shah

Hello everyone,

We have around 15 to 20 plug-ins developed the in VB .Net and would like to upload them to CRM via Developer Toolkit in VS 2012. We have referred and tried following two URLs for the same but unable to deploy the plug-in successfully to CRM.

blogs.msdn.com/.../building-vb-net-plugins-with-the-developer-toolkit.aspx

blog.davehawes.com/.../How-to-put-Early-Bound-Entities-in-a-separate-project-and-merge-it-with-Plugin-and-Workflow-projects-in-Crm-Dynamics-2011.aspx

When we try to deploy it from Deploy solution we are getting the command error for entire ILMerge command to with Exited with code 9009.  Do anybody also face the same problem?

Any help would be much appreciated.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Nina P. Profile Picture
    Nina P. 2,195 on at

    Hi Ankit,

    thank you for using Dynamics CRM Community. I understand that you are experiencing issues to upload your VB. NET plugins to CRM via Developer Toolkit.

    As documented in the Know Issues section of the Developer Toolkit readme file available in SDK 2013 under SDK\Tools\DeveloperToolkit\Scenario Developer_Toolkit_readme.htm, the Developer Toolkit does not support Visual Basic .NET.

    I would recommend you to use the CRM Plugin Registration Tool instead to successfully deploy your plugins or alternatively rewrite your plugins from VB. NET to C# , if you find that you’d benefit using the Developer Toolkit for your particular scenario.

    Please let us know if this helps.

    Nina Peneva

    CRM Support Engineer

  • Ankit Shah Profile Picture
    Ankit Shah on at

    Hello Nina,

    Thank you for the response.

    But, in the first URL that I specified in my question, they are deploying VB .Net plugins via developer toolkit. Did you check that post?

  • Suggested answer
    Nina P. Profile Picture
    Nina P. 2,195 on at

    Hi Ankit,

    thank you for your answer. I have checked the first URL which you have specified in your question.

    When we document or state that a certain scenario is not supported, doesn't necessarily mean that this is not going to work; it means that this scenario wasn't (fully) tested and verified and if it fails, we would not be able to investigate it and request a fix for it. Therefore I recommend you to use the CRM Plugin Registration Tool instead to successfully deploy your plugins or alternatively rewrite your plugins from VB. NET to C# , if you find that you’d benefit using the Developer Toolkit for your particular Scenario, as mentioned in my previous post.

    Please let us know if this helps.

    Nina Peneva

    Support Engineer

    Microsoft Dynamics CRM

  • KeithHoward Profile Picture
    KeithHoward on at

    Hello Nina,

    Actually, I am having the same problem. Our entire code base (roughly 30 projects) is in VB.NET uniformly. One of these projects contains our CRM plug-ins, in VB.NET. We have struggled a lot to take advantage of the smooth plug-in deployment process that is available via the SDK. It does not seem logical that we cannot create C# wrappers to invoke each of our VB.NET plug-ins. Logically, IT HAS TO WORK, but we have not been able to figure it out. I hope that you can understand that it is awkward to have to migrate only one of our 30 projects to C#. That has sweeping ramifications for code maintenance (e.g., global replaces become problematic, etc).

    I understand your response that the official MS platform is that we should use C#, but the reality is as I have described above. Do you think that I might be able to progress this issue via an MSDN call?

    Many thanks for your understanding.

    Kind regards,

    Keith

  • Nina P. Profile Picture
    Nina P. 2,195 on at

    Hi Keith,

    many thanks for your post. As my colleagues from CRM  Technical Support would suggest you the same, I  encourage you to send a product suggestion at  https://connect.microsoft.com/ instead and provide insight to the Microsoft development community about your scenario and the importance of the VB.NET Support.

    Thank you for your understanding and for using Microsoft Dynamics CRM Communities.

    Nina Peneva

    Support Engineer  

    Microsoft Dynamics CRM

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans