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/
Related
I plan to use the Microsoft.Azure.NotificationHubs to push notification through Azure notification hub in backend service of an existed project. However, I found that the project is using .NETFramework 4.5.2. As the document stated, the SDK has dependecy to .NETFramework 4.6.1 or higher.
Since the existed project is already developed well and problems could appear if I upgrade. Any other solutions please?
Due to you don't want to upgrade to .Net Framework 4.6.1 or higher. You can use REST API, create HttpClient in your existed project to send Http Request.
（notificationhubs）REST API methods
You can use HttpHelper in my sample code.
Is there an easy way to download the latest Universal package contents without running all the commands using the Azure CLI ?
In my project, we are storing the Installer generated from pipeline (of a .NET application) as a Universal Package in the Azure Artifacts. This is a ZIP file containing the Installer.
While it was easy to download the Zip file in TeamCity, it's a headache in Azure Devops. 30 people in my team has to download the Installer every week and we are looking for an easy way to download this (at least the latest universal package).
Is there an easy way to download the latest Universal package contents without running all the commands using the Azure CLI ?
To download the Universal package in Azure Devops, we could use the Universal packages task：
We could use wildcard in the Version option to get the highest version with major version.
BTW, there is an user voice about use the REST API to download the Universal package. If there is a REST API available, the ERST API will also be a good choice. You could vote that that up and leave your comment.
Using LINQPad I've added a private feed to Visual Studio Team Services. However one of my packages requires a pre-release package: Quartz.Net in my case. I've ticked Include Prerelease but I think it's getting confused and trying to load the package from my private feed rather than NuGet.
I've tried to work around the issue by loading the package into the local package cache. LINQPad doesn't seem to consider this. Other than uploading these packages into my own private feed, what options do I have? I'm not going to alter my own packages to get around LINQPad's shortcomings.
Note: I've setup the VSTS feed according this question.
Here is what my NuGet feeds look like in LINQPad
Changing the package to pre-release fixes this issue, and add the pre-release packages dependencies to my own feed.
Now LINQPad attempts to add the package. Mind you I now get another error;
"There are no usable .NET assemblies in package
'MyPackage.Common(Prerelease)'
That's down to NET Standard & NET47 support.
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
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?