search

unchase / Unchase.Odata.Connectedservice

:scroll: A Visual Studio extension for connecting to OData services with generating client-side C# proxy-classes
Apache License 2.0
44 stars 13 forks source link

Support update from Odata Connected Service #5

Closed marcioafoliveira closed 5 years ago

marcioafoliveira commented 5 years ago

I have a service that I created with Odata Connected Service on VS 2017. I can add a new one but I can't update it.

We really need this feature.

unchase commented 5 years ago

Did you create the file with Unchase Odata Connected Service or with Odata Connected Service by Microsoft? Can you re-generate the specification file (by creating it again) and try to update it?

marcioafoliveira commented 5 years ago

OData Connected Service by Microsoft

unchase commented 5 years ago

My service cannot update the client-code created by the OData Connected Service by Microsoft, because they have different productId (providerId) of the Connected service. Instead, you can re-generate the code from an existing json-specification URI using my service, and then update it when required.

But I will see if I can somehow to solve this issue.

marciooliveiraprimaverabss commented 5 years ago

updates?

unchase commented 5 years ago

Hi, @marcioafoliveira.

It will be ready in the next release.

unchase commented 5 years ago

Fixed in v1.3.0.

unchase commented 5 years ago

Why do you need the ability to update client code with an unsupported Connected Service by Microsoft when you can generate it using the Unchase OData Connected Service, and update it later when you like? The generated code will not differ so much that compatibility is broken.

I added a button so that you can load similar data from a json-file to generate client code.

HASSEN-MEDDEB-ATOS commented 4 years ago

Hello,

I have issue OrgContext not generatd in reference.cs, can anyone help me please

Cordially