System.ServiceModel.Description.TypeLoader.AddBehaviorsAtOneScope

[antsaia]

I'm referencing these libraries in a .NETCORE2.0 project built to run on AWS Lambda. I need to get this working and wondering if you have any suggestions.

I'm getting an error that Operation is not supported on this platform.: PlatformNotSupportedException
at System.ServiceModel.Description.TypeLoader.AddBehaviorsAtOneScope[IBehavior,TBehaviorCollection](Type type, TBehaviorCollection descriptionBehaviors, ServiceInheritanceCallback2 callback) at System.ServiceModel.Description.TypeLoader.AddBehaviors(ContractDescription contractDesc, Type implType, Boolean implIsCallback, ContractReflectionInfo reflectionInfo) at System.ServiceModel.Description.TypeLoader.LoadContractDescriptionHelper(Type contractType, Type serviceType, Object serviceImplementation) at System.ServiceModel.Description.TypeLoader.LoadContractDescription(Type contractType) at System.ServiceModel.Description.ContractDescription.GetContract(Type contractType) at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient1.CreateBaseServiceEndpoint(Uri serviceUrl, TimeSpan timeout)
at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient1.CreateServiceEndpoint(Uri serviceUrl, Boolean useStrongTypes, TimeSpan timeout, Assembly strongTypeAssembly) at Microsoft.Xrm.Sdk.WebServiceClient.WebProxyClient1..ctor(Uri serviceUrl, Boolean useStrongTypes)

[Lxiamail]

@antsaia Can you provide the repro program which ran into the issue?

[rstraszewski]

I had similiar problem, when I had contract with contract behavior as attribute. When I configured behavior in code (on channel factory), the problem was gone.

[Lxiamail]

@rstraszewski Can you share a simple repro?

[rstraszewski]

@Lxiamail
https://github.com/rstraszewski/WcfCoreTestClient/blob/master/WcfCoreTestClient/Program.cs

It would be great, if it also worked for attributes - in our company, most of behaviors is set this way. It would make migration to .net core much easier.

[samlh]

It would also be fine if we could disable the error message, and add the behavior manually, so that we could still use existing service definitions without having to make changes to the services.

[rstraszewski]

Yep, ignoring attributes, instead throwing exceptions also would be ok - it would make migration simpler.

[rstraszewski]

@Lxiamail
Any plans regarding support of attribute based behaviors?

[Lxiamail]

@rstraszewski Hope we can support it in the next release.

[Lxiamail]

The fix has been checked in by #3529