- We have 2 orgs running in our on-premise crm 2011 system.
- We have generated early bound classes for both orgs.
- One of our plugins is throwing the “a proxy type with the name account has been defined by another assembly” error when deactivating an account.
- That plugin only references one of the early bound dll’s.
How do I get the CRM system to respect the namespace of these references.
I’ve tried the few items that show up from Google and none are working.
Since you can reproduce this with 2 vanilla orgs I would imaging there is something OUTSIDE the code layer we can do without having to go back and refactor a bunch of code for the 2 orgs.
Thanks,
Jon
this normally means that there is one or more assemblies with the same method name or property to fix this use the fully qualified name of the assembly.. for example in the using System.IO for example if you had a method named the same way in your Class code that conflicts with System.IO…. you would write your fix like
thisObject.System.IO.Path( —- ) = somthing for example.. does this make sense..?