Skip to content
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

Adding OData Connected Service to the project failed: Unable to load the service index for source https://www.nuget.org/api/v2/. #77

Open
AlexRozen opened this issue Dec 6, 2017 · 1 comment

Comments

@AlexRozen
Copy link

AlexRozen commented Dec 6, 2017

Our enterprise network is isolated from the Internet.
My VS 2017 NuGet manager is configured to use only local package sources.

Now I have the subjected problem. I hope, that all needed packages are manually downloaded to the local storage. But this VS setting seems to be ignored by OData.ConnectedService.
P.S. My OData source is V3. Source code shows that V3CodeGenerator has completely different logic for package locating.
P.S. Locally I have:
microsoft.data.edm.5.6.3.nupkg
microsoft.data.edm.5.8.3.nupkg
microsoft.data.odata.5.6.3.nupkg
microsoft.data.odata.5.8.3.nupkg
microsoft.data.services.client.5.6.3.nupkg
microsoft.data.services.client.5.8.3.nupkg
microsoft.odata.client.6.17.0.nupkg
microsoft.odata.client.6.19.0.nupkg
microsoft.odata.core.6.17.0.nupkg
microsoft.odata.core.6.19.0.nupkg
microsoft.odata.core.7.3.1.nupkg
microsoft.odata.edm.6.17.0.nupkg
microsoft.odata.edm.6.19.0.nupkg
microsoft.odata.edm.7.3.1.nupkg
microsoft.spatial.6.17.0.nupkg
microsoft.spatial.6.19.0.nupkg
microsoft.spatial.7.3.1.nupkg
system.spatial.5.6.3.nupkg
system.spatial.5.8.3.nupkg

@unchase
Copy link

unchase commented Feb 19, 2019

You can try my Unchase OData ConnectedService for solve this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants