Publish to NuGet #25

New issue

Open

opened 2014-12-02 11:09:55 -08:00 by ddaws · 2 comments

ddaws commented

2014-12-02 11:09:55 -08:00

(Migrated from github.com)

I believe this would make it simpler to use. See reference for how to here : http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package

I would take care of this though publishing packages requires a NuGet API key and I want to leave control of publishing to NuGet to @andyburke .

I believe this would make it simpler to use. See reference for how to here : http://docs.nuget.org/docs/creating-packages/creating-and-publishing-a-package I would take care of this though publishing packages requires a NuGet API key and I want to leave control of publishing to NuGet to @andyburke .

andyburke commented

2014-12-04 18:47:27 -08:00

(Migrated from github.com)

@dreid93 feel free to publish this now that I've made you a collaborator.

ddaws commented

2014-12-06 08:18:49 -08:00

(Migrated from github.com)

So I have just uploaded it to NuGet. I have yet to test so I will be leaving this issue open until I can confirm that everything is working.

Here's the link : https://www.nuget.org/packages/UnityHTTP/1.0.0

Also, NuGet contains a way to specify references based upon the framework you building towards. This should fix some of the issues people are having.

So I have just uploaded it to NuGet. I have yet to test so I will be leaving this issue open until I can confirm that everything is working. Here's the link : https://www.nuget.org/packages/UnityHTTP/1.0.0 Also, NuGet contains a way to specify references based upon the framework you building towards. This should fix some of the issues people are having.