Create NuGet packages for all assemblies in the Windows Azure SDK
Today there are official NuGet packages for some of the assemblies in the Azure SDK like Service Bus and Configuration Manager. Others are missing, like Service Runtime. There are some community contributed packages, but I prefer official ones.
The motivation for NuGet packages is the same as always:
* you automatically get the needed changes in your app/web.config
* you can more easily change the version number of the assembly that you like to use, in the package.config and then push to your VCS. Compare this with reinstalling a new version of the SDK on every developer/CI/build machine.
* the solution becomes more self-sustained, you don't have to install the SDK at all, easier to build and easier to deploy
Johan Karlsson
shared this idea
We are currently investigating the opportunities around shipping more features as NuGet packages. We have opened up far more areas as NuGet packages than in previous releases. That said, the idea of creating a NuGet package that contains the emulator is a large effort. As we progress towards this goal or realize that it isn’t possible I’ll update the forum thread.
For the time being, rest assured we’ve heard this comment, which has been echoed by the larger Windows Azure community. As an Azure developer myself I find merit in this request and feel there is a good chance it could eventually be realized.
2 comments
-
Thomas Lee
commented
Please consider making these packages availailble via OneGet (part of PowerShell V5).
-
628426
commented
The friction between multiple installed version of the SDK, projects directly referencing %PROGRAMFILES&/Azure SDK/2/2.1 etc, as well as using NUGET for Storage Client is a real headache. I vote for the SDK to be all NUGET based, and developers who want them download the tools (emulator, VS add-in)