-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request to allow an option to use existing models in particular namespaces. #67
Comments
Hi, @jimnkey Could you please demonstrate with a specific example what exactly you are cleaning up? |
Thanks for responding so quickly....
Then consuming the metadata endpoint and keeping the same namespace
Leaving Default.Container as is in the project to be used by clients that can bring in that client project. (did not include edm xml here)
|
As a side note ... I did try to generate the template files but I must have been doing something wrong -- I could not get them to properly generate. But now we're working with 2022 with the projects migrated already. And find we need to add an entity :) |
Great work with this library! Thank you!!!
Having the need to share the models from one project with the OData infrastructure and the rest of the solution.
The models are used in other projects that should not (must not) bring in OData. Right now we manually gut out the generated portions of Reference.cs that are already defined but leaving the skeleton partials and creates along with the Container. That seems to work well - but creating or updating entities becomes a bit tedious. Although manageable, it would be very nice...
Is this feature already available (somewhat) by not creating the models and somehow registering the models with the Container externally?
Any chance this was a planned feature? :) along with the 2022 support?
Thanks again!
The text was updated successfully, but these errors were encountered: