Service Client and Early Bound generation

[Kevmscotland]

Previously I've used the CrmSvcUtil to generate EarlyBound classes which creates the OrganisationServiceContext (which requires the old IOrganisationService).
This enables me to keep everything strongly typed and use Linq queries for data retrieval etc.

Is there a proposed way or guide on how to go about generating Earlybound classes to create a Context for using the new Dataverse Service Client?

[MattB-msft]

it works exactly the same.
Just pass the Dataverse ServiceClient to the OrganizationServiceContext.

[BetimBeja]

Isn't it easier trying than asking... you lose 10 minutes to try... and make a lot people lose time following this type of question 😞

[Kevmscotland]

Its a good discussion point. Now other people who may not have known now have the answer thanks to Matt. 😄

[MattB-msft]

Yes code generated by crmsvcutil is .net core compatible.

We also released and update to the generator to try to help prevent folks from running into issues with messages that use unreleased types.

[xairrick]

I normally use the generator that is in the XrmToolbox (which I believe uses the CrmSrvUtil) and have found the early bound classes & context work without any modifications in .NET Core 3.1. The only thing that worries me is that the OrganizationServiceContext is using IOrganizationService and not IOrganizationServiceAsync or IOrganizationServiceAsync2

[jordimontana82]

@sabrish, yeah, they were .net core compatible since first time I tried back in Feb 2020 :)