You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which one should we use? Which one is still maintained? Why are there two available anyway?
Background
I already know having installed both at the same time is a bad idea because it messes with the templates or whatever they do. However, even separately, I cannot get any of them to create an OData client for me.
OData Connected Service
Only shows an error message if you try to access a development server with a self-signed HTTPS certificate, but doesn't give clear details on why it couldn't find the metadata resource.
Simple enough, switch dev server to HTTP and think you're done, but...
Throws possibly bogus error if it finds NavigationProperties. .
I now try narrowing down the navigation properties since it seems to work if I remove all dependencies and slowly add them back, one after another. It's sad it doesn't show which property exactly caused the issue, this would really help me. If I found the root cause, I'll post the relevant metadata here (I can't now because it shows too much of our company's database and I'm not allowed to post that).
Simply doesn't create a new item in the "Add New Item" dialog for me. Tried to add an item to a .NET Framework and .NET Core library project, wasn't in both lists. Renders it useless for me.
Additional detail
I'm using VS2017 Professional with the latest updates.
The text was updated successfully, but these errors were encountered:
RayKoopa
changed the title
Please give clear instructions on which extension to use - both don't work
OData Client Generation, please give clear instructions on which extension to use - both don't work
Aug 27, 2018
@RayKoopa - The connected services offers you a UI to generate the client code whereas the client code generator needs parameters to be set explicitly. In the future, one of the tools will be deprecated.
You can refer to the workaround mentioned in #1225 . That issue has been fixed and should be available in the next release for that package but in the meanwhile feel free to use the workaround.
I believe that there is more investigation needed for OData/lab#76. Although I suspect that client code generator would also see the same issue, but it may be worth trying.
Thanks, I'll stick with the Connected Service one then, because the other one, for some reason, doesn't yield me a new template in the Add New Item dialog.
Short summary (3-5 sentences) describing the issue.
You offer the following 2 extension on the VS marketplace:
Which one should we use? Which one is still maintained? Why are there two available anyway?
Background
I already know having installed both at the same time is a bad idea because it messes with the templates or whatever they do. However, even separately, I cannot get any of them to create an OData client for me.
OData Connected Service
Simple enough, switch dev server to HTTP and think you're done, but...
.
I now try narrowing down the navigation properties since it seems to work if I remove all dependencies and slowly add them back, one after another. It's sad it doesn't show which property exactly caused the issue, this would really help me. If I found the root cause, I'll post the relevant metadata here (I can't now because it shows too much of our company's database and I'm not allowed to post that).
EdmxReader
was renamed toCsdlReader
.OData v4 Client Code Generator
Additional detail
I'm using VS2017 Professional with the latest updates.
The text was updated successfully, but these errors were encountered: