DynamicEdmModelCreation not working in V6
I wondering if anyone has sucessfully mananged to build & run DynamicEdmModelCreation project in V6/6.1 beta?
Hi @samualjacksonau what issues/errors are you running into? I'm asking because we also have a dynamic edm model project and is planing to move to V6.
Hi folks,
even if this issue is a little bit older: I just updated all dependencies of the DynamicEdmModelCreation sample to their latest versions and the following issues/errors occur.
Microsoft.OData.Core 7.4.1 Microsoft.AspNet.OData 6.1.0
-
HandleAllController:- The class
PropertyAccessPathSegmentdoes not exist anymore. - The class
NavigationPathSegmentdoes not exist anymore.
- The class
-
CustomODataPathRouteConstraint:- The class
ODataPathRouteConstraint:- Only has a constructor that accept one parameter: the route name.
- The property
PathHandlerdoes not exist anymore.
- The class
HttpRequestMessageProperties:- The property
Modeldoes not exist anymore. - The property
PathHandlerdoes not exist anymore. - The property
RoutingConventionsdoes not exist anymore.
- The property
- The class
ODataExceptionmoved to another namespace.
- The class
-
MatchAllRoutingConvention:- The class
NavigationPathSegmentdoes not exist anymore. - The class
KeyValuePathSegmentdoes not exist anymore. - The class
EntitySetPathSegmentdoes not exist anymore.
- The class
The rest is only changed or no longer existing namespaces.
Cheers, Matt
Hi folks,
I just added a comment in another issue that also addresses this problem.
See: https://github.com/OData/ODataSamples/issues/50#issuecomment-371590377
I'll take a look and hope to update the sample soon.
Cheers, Matt
Hi folks,
I just added a pull request which fixes the dynamic model creation sample for v6. :-)
Pull Request: #67
Cheers, Matt
Hi Guys, :-) It seems you all already worked much in EDM dynamics model. I recently created one issue, just wanted to know, if anyone of you face this issue #70 , where child/asociate record not coming in result?
Thanks.
All Seems this has been open for a while - I have managed to get the EDM Dynamic Model working with 7.3 in DotNetCore 3.1 based on this article, however I notice that the ServiceDocument (based on the /odata/ default route) does not work...not sure it ever did in 2.2 ?
Any hints or direction on resolving this would be great!
It seems updating the samples would be of great value to the community as a whole - as the basic use cases I real usage are probably more an exception than the rule, and this and the other samples provide a great starting point for real usage scenarios.