Home → Questions →

How do I publish a solution to MyGet?

• Edit

Pure Krome

01 Nov, 2014 12:01 AM

Hi,

i've manually published packages many many times up to (the official) NuGet gallery. I know about nuspecs etc.

Now, I'm trying to utilize MyGet for in development packages. I've followed this post to setup my settings .. so that's fine ..

but I'm not sure about how AppVeyor knows how to use nuspecs or whatever. I don't understand the connection between the two.

Are there some doc's that can explain how I tell AppVeyor that this is my nuspec or whatever and that's used to make the package which you then push up to MyGet?

1. Support Staff 1 Posted by Feodor Fitsner on 01 Nov, 2014 12:30 AM

   

   There is only very narrow scenario currently supported: http://www.appveyor.com/docs/nuget#auto-package, i.e. when there is .nuspec file in the root of project.

   • Edit

2. 2 Posted by Pure Krome on 01 Nov, 2014 12:51 AM

   

   What about multiple .nuspec files?

   Would you consider adding in an optional setting in the project settings, that allow us to define the folder where the nuspecs are? (I don't like spamming the root folder with nuspecs and instead put them in a folder called NuSpecs or whatever).

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 01 Nov, 2014 12:56 AM

   

   Yeah, NuGet automatic packaging should be definitely improved. Could you please describe in more details your use case?

   • Edit

4. 4 Posted by Pure Krome on 01 Nov, 2014 01:38 AM

   

   Sure :)

   here's a screenshot I've cooked up in 1 sec.
   

   So this is the use case :-

   1. Create a few nuspecs for my solution into a folder called NuSpec Files or whatever (the point here is that there could be a space in the folder name)
      
   2. Commit new code, push up to GH.
      
   3. On successful build and test, pack those nuspecs and push up to MyGet.

   later on, then do an environmental push to NuGet.

   I'm making a pretty big convention call here and that is that there's only one folder to contain all the nuspecs. Improving on this, there could be a default list of paths.

   eg.
   Root folder : \
   1st Attempt: \NuSpecs
   2nd attempt: \NuSpec Files
   .. etc...

   • Edit

5. Support Staff 5 Posted by Feodor Fitsner on 04 Nov, 2014 02:15 AM

   

   OK, I see. Thanks for sharing your thoughts. Right now deployment in AppVeyor follows some kind of "build once deploy everywhere" concept, i.e. your first push everything to artifacts and then deploy from artifacts only. So, in case of NuGet I think we could improve packaging NuGet package artifacts by specifying locations with ready packages.

   • Edit

6. 6 Posted by Pure Krome on 05 Nov, 2014 11:37 PM

   

   is there a road map or issue tracker so I can see if a suggestion like this (the ability to define a location of .nuspec files) is on the todo list and the progress of it?

   • Edit

7. Support Staff 7 Posted by Feodor Fitsner on 06 Nov, 2014 12:15 AM

   

   Yes: https://github.com/appveyor/ci/issues

   • Edit

8. 8 Posted by Pure Krome on 07 Nov, 2014 12:30 AM

   

   May I add this question there, as an issue please, so I can keep track of it, etc?

   • Edit

9. Support Staff 9 Posted by Feodor Fitsner on 07 Nov, 2014 12:40 AM

   

   Sure!

   -Feodor

   • Edit

10. Pure Krome closed this discussion on 29 Jan, 2015 04:18 AM.