Home → Questions →

Trying to build a NuGet package that has mutliple-sln's-per-framework

• Edit

Pure Krome

29 Feb, 2016 10:31 PM

Hi Feodor :)

I've been asked to generate a nuget package which will contain multiple dll's - one per framework.

eg.
- NET35.dll - NET4.dll - ..etc..

I know how to do the nuget side of things, given the dll's.

I'm not sure how to generate / build the dll's with AppVeyor. Currently, they have a single solution per framework.

eg.
- NET3.5.sln - NET4.0.sln etc.

The solutions are pretty simple (for what it's worth).

Do you have a suggestion on the way/recommendation I should go with creating this AV project?

Initially i thought of a single AV project per sln. But that won't help for the auto-publishing the nuget package because each project will not have all the dll's required, for the pack/publish steps.

Cheers!

-PK-

1. Support Staff 1 Posted by Feodor Fitsner on 01 Mar, 2016 12:46 AM

   

   You can just have build step defined as a "Script" with commands for each platform, kind of:

   build_script:
   - msbuild NET3.5.sln
   - nuget pack ...
   - msbuild NET4.0.sln
   - nuget pack ...
   

   • Edit

2. 2 Posted by Pure Krome on 01 Mar, 2016 01:20 AM

   

   Ah! ok. so manually list each msbuild command (and add the special AV logger too..)

   I only want to have 1 nuget package pushed up to NuGet with all the dll's (per framework) in there, so I shouldn't nuget pack .. after each build, right? that will create a seperate nuget package, each time?

   maybe i should copy the dll's from the output of the msbuild instead, to a temp location and then have my nuspec reference those?

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 01 Mar, 2016 01:57 AM

   

   Oh, right, there should be one nuget pack command only.
   As far as I know you can collect assemblies into nuget package from different folders, no need to copy them into temp location.
   -Feodor

   • Edit

4. 4 Posted by Pure Krome on 01 Mar, 2016 01:58 AM

   

   Oh yeah of course. just refence the \release folder, etc.

   ha yeah. kewl.

   ta! case closed :)

   • Edit

5. Pure Krome closed this discussion on 01 Mar, 2016 01:59 AM.