FakeXrmEasy.365 has a missing dependency to Microsoft.CrmSdk.Extensions when .InitializeMetadata(Type) is used.

[jordimontana82]

It seems that when using latest version of FakeXrmEasy.365 and using the above method to init metadata from early bound types, it's complaining about this missing reference probably because type is still in use, although deprecated now.

That class exists in the (now deprecated) is in Xrm.Client namespace which seems to exist in the Microsoft.CrmSdk.Extensions package.

I think it would be better to include that package dependency in the .nuspec file but with a view of getting rid of it eventually...

Also:

• When generating option sets, the OptionSet property generated is null, we could generate a dummy one, that can be then overriden if needed
• Similarly for the Targets property when generating Lookups. It's null. We could generate it as an array with a single dummy value as the target.

Thoughts ? @BetimBeja

[BetimBeja]

Perhaps we could track usage in the package and change the condition to

#if FAKE_XRM_EASY || FAKE_XRM_EASY_2013 || FAKE_XRM_EASY_2015

and drop those parts of the code from the crm >=v. 8

The package Microsoft.CrmSdk.Extensions seems "abbandoned" to version 7.1.0.1

[jordimontana82]

Yep, sounds good

[BetimBeja]

I have done some quick check of uses of the Xrm.Client namespace and the only required change is the line you specified here.
The other references are being correctly handled with the proposed solution

[jordimontana82]

Grand, I've found a few other bits that might be interesting in metadata generation from early bound types, I'll add them to the issue description