-
Notifications
You must be signed in to change notification settings - Fork 3
Producing NuGet Packages (v2)
Darrell edited this page Dec 13, 2015
·
3 revisions
This is for DnnPackager v2 and onwards. Things were handled slightly differently in v1
DnnPackager adds a "Solution.nuspec" file to your Solution that looks like this:
<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
<metadata>
<id>DotNetNuke.SolutionPackages.MySuperModule</id>
<title>MySuperModule DotNetNuke Solution Packages</title>
<version>0.0.1</version>
<authors>Darrell Tunnell</authors>
<owners>Darrell Tunnell</owners>
<licenseUrl>https://github.com/dazinator/DnnPackager</licenseUrl>
<projectUrl>https://github.com/dazinator/DnnPackager</projectUrl>
<requireLicenseAcceptance>false</requireLicenseAcceptance>
<description>Contains the MySuperModule solution packages</description>
</metadata>
<files>
<!--This should be updated to reflect the output path of your module install zip-->
<file src="\*.zip" target="Content" />
</files>
</package>
All you need to do is modify it appropriately, and add to the files
section, the paths to your module installation zips for each module you want to include in the NuGet package.
<files>
<!--This should be updated to reflect the output path of your module install zip-->
<file src="\MySuperModule\bin\release\MySuperModule.zip" target="Content" />
<file src="\MyOtherModule\bin\release\MyOtherModule.zip" target="Content" />
</files>
Then when you want to produce the NuGet package, call NuGet.exe Pack
command on the NuSpec file.
This will produce you a NuGet package containing all of your installation zips for you to put on whatever nuget feed you want.