You’re offline. This is a read only version of the page.
247
Hello,
I am working on project work to setup the D365 online instance but based on a CRM 2011 code base which uses early binding classes.
Can I get some help with generating the early binding ServiceContext (Entity.cs) and mainly the OptionSet.cs file as to whether I should be using the “EarlyBind Generator tool” of the XRMToolbox or the native SDK based utility crmsvcutil.cs.
For the native SDK option, I may to find a way to change the "local Option Set Format" to have "_" in between them as the default one from SDK comes as {0}{1} for Entity Schema Name ({0}) and Attribute Schema Name ({1}). Can I get help with this one part too?
Thanks in advance, AR
Hello AR,
Could you explain you question a little bit better? Because I don't understand wat you want from us.
Is the main question "Which early bound generator should I use, XRMToolbox or the native SDK based utility?"?
Answer:
This depends on you preference. XRMToolbox Early bound generator is an UI wrapper around crmsvcutil.exe. So everything XRMToolbox Early bound does can be done with crmsvcutil.exe.
The great benefit of XRMToolbox Early bound is that is saves the configuration in a nice settings file which can be stored in a versioning system. In this way you or your team members can easily extend the existing solution.
I don't understand wat you want to say in you last paragraph about "local Option Set Format".
Share
Report
All responses (
Answers (
