The samples I've found so far use either
repository.FindPackage()
or
repository.GetUpdates()
But both a v2 of the NuGet .NET API. Where can I find an example of equivalent for v3?
Related
does anyone knows a good documentation for nuget service endpoints?
I'm looking for it for both nuget v2 and v3 (v2 in priority as V3 is still in contruction).
Updating several years later: There is now official documentation for the NuGet server API over at microsoft.com.
There is no official documentation of NuGet API, but since NuGet is open source, you can take a look here: https://github.com/NuGet/NuGetGallery
The API requests handling code is located in this file:
https://github.com/NuGet/NuGetGallery/blob/master/src/NuGetGallery/Controllers/ApiController.cs
I am working on Web Api with OData enabled. I started working by referring to (only the relevant dlls to the question are mentioned)
Microsoft.AspNet.WebApi.OData
Microsoft.Data.OData
Microsoft.Data.Edm
System.Spatial
But when I found out OData is by default case-sensitive, I look for a solution of case insensitive and I have gone through few post Support OData Uri case insensitive parse & ODataLib 6.7.0 Release then finally landed into nuget package Microsoft.OData.Core 6.9.0 which seems to be solving my problem. Here my confusion starts, It has its own collection related libraries under different namespace
Microsoft.OData.Core-----------VS------Microsoft.Data.OData
Microsoft.OData.Edm------------VS------Microsoft.Data.Edm
Microsoft.Spatial--------------VS------System.Spatial
What is difference between above similar libraries, where we should use one upon another? In similar cases of mine, Microsoft.OData.Core can be use instead of Microsoft.Data.OData which is solving case sensitive issue?
1. About the namespace,
Microsoft.Data.OData
Microsoft.Data.Edm
System.Spatial
are the implementation of OData Version 3.0 Spec. The package name on Nuget end with OData v1-3. For example: ODataLib for OData v1-3
While,
Microsoft.OData.Core
Microsoft.OData.Edm
Microsoft.Spatial
are the implementation of OData Version 4.0 Spec. The package name on Nuget don't contain version . For example: ODataLib
2. About the case-insensitive
Web API OData will support case-insensitive, unqualified function/action call and Enum prefix free in the 5.4 release.
Here's a simple example you can refer to.
The source codes are moved to:
WebAPI OData on Github
And you can get the binary from nightly build.
We are planning to upgrade our app from V2 to V3. I have read all the documents but there is nothing specific saying the issues of moving V2 to V3. V3 is REST based and V2 was based on QBXML so anything specific you want developers to note for upgrading the code to support V3? Also any upgrade tool would be awesome that can replace V2 to V3 would be very helpful to developers.
You can refer the following docs -
https://developer.intuit.com/docs/0025_quickbooksapi
https://developer.intuit.com/docs/#api/deki/files/1463/gettingstartedwithquickbooks.pdf
JAVA/C#/PHP devkits and usage details are available here -
https://developer.intuit.com/docs/0025_quickbooksapi/0055_devkits
PN - V2 and V3 both are REST based APIs.
If you have any entity specific qts then you can post it in IPP's live community.
https://intuitpartnerplatform.lc.intuit.com/
Thanks
There are some entities that are supported in V2 that are not yet supported in V3. Is there any guidance on how to use both V2 and V3 in the same app?
A hybrid model for v2 and v3 is not supported as the assembly names might conflict in the same project. You can use 2 different projects in same namespace to access v2 and v3 separately.
As of now the latest version of the Exchange Web Services Managed API is 2.0. The only package on nuget is http://nuget.org/packages/Microsoft.Exchange.WebServices/ which is 1.2.
What is the proper way to bring the latest managed api to nuget? Do we have to request a package from Microsoft? Is it legal to create a package and push it to nuget?
Since there are many Microsoft libs on nuget that have been packaged by 3rd parties, I decided to go ahead and put it up there: https://www.nuget.org/packages/EWS-Api-2.0/