Recently I have been trying to generate more Nuget packages for our dotnet core projects, utilizing the
dotnet pack command. One issue I have been encountering is that the command was either referencing the required nuget packages, or the project reference DLLs, never both.
The current problem.
If you have Project A which has a project reference to Project B as well as including a nuget package called Package A you would expect the generated package to contain a link to both the required nuget package, and the DLL(s) for Project B, yes? This however is not how the dotnet pack command works.
This issue is widely reported on their repo (I.e. https://github.com/NuGet/Home/issues/3891 ) and unfortunately it seems the developers and the community are in a bit of a disagreement to what is “correct”. The official stance (as I understood it) is that the project references won’t be included as they should be their own packages. This however is not always practical or desired.
Plenty of workarounds have been suggested around Stack Overflow and Github including having a seperate nuspec file, using Powershell to inject things into the generated nupkg and so on…
The solution below worked for me, but of course, YMMV.
In the end I ditched having my own
.nuspec file within my project (as per some SO posts) and instead used the CSPROJ (as recommended). Below you can see the required fields for the packaging (version, naming, etc), a reference to a nuget package, and a reference to another project within the solution.
If you run dotnet pack now, it will generate an appropriately named package which will contain a nuget dependancy on
SomeNugetPackage. This can be confirmed by opening the nupkg with an archive tool (7Zip,WinRar, WinZip…) and seeing that the only DLL in the
lib folder will be the DLL of the project being packed.
The fix is as follows:
- Alter the project reference to set the
ReferenceOutputAssemblyflag to true, and
IncludeAssetsto the DLL name
<ProjectReference Include="..\ProjectB.csproj"> <ReferenceOutputAssembly>true</ReferenceOutputAssembly> <IncludeAssets>ProjectB.dll</IncludeAssets> </ProjectReference>
- Add the following line into the
- Add new target between
<Target DependsOnTargets="ResolveReferences" Name="CopyProjectReferencesToPackage"> <ItemGroup> <BuildOutputInPackage Include="@(ReferenceCopyLocalPaths->WithMetadataValue('ReferenceSourceTarget', 'ProjectReference'))"/> </ItemGroup> </Target>
So now you end up with something that looks like this
Now if you run dotnet pack you should see any project reference DLL under the
lib folder of the package, and if you inspect the nuspec file inside the package (or upload it to your package repo) you should see the nuget dependencies.
Hopefully this helps someone, as there is a lot of conflicting info around. Please let me know if this would cause any issues!
The post Include both Nuget Package References and project reference DLL using “dotnet pack” 📦 appeared first on yer.ac | Adventures of a developer, and other things..
Top comments (10)
Wanted to cross-reference a similar implementation on SO - stackoverflow.com/a/59893520/968003.
BTW, in order to bring XML-docs add
BuildOnlySettingsto "Target DependsOnTargets". It also will add
*.snupkgif you generate one.
So the final snippet looks like:
This worked great for the project dll to be included but did not add the packages references for the packages referenced form ProjectB.dll
Thanks, it looks like promising solution!
However I found one not fully solved issue with it.. It copies all needed files correctly and it works in general, but it still adds a package reference to not existing package inside generated *.nuspec file.
Trying to restore "master" NuGet package from Visual Studio - it's trying to find the dependent (not existing) package, and obviously fails. However if I add the "master" package manually through *.csproj file - it's added and can be successfully restored. There is also no resolved code - so everything works. Except some better tooling support..
Nevermind.. seems like "ProjectB.dll" did the work, and now it works more correctly. I just didn't want to reference a dll in a "hardcoded" way initially..
Thanks! Solved my issue today :)
I managed to get it working without those lines:
Could you please share your solution?
thanks a lot for this solution. I like it to structure my nuget solutions in projects.
Is there a way to include the xml doc files form the referenced projects into the nuget.
This would make IntelliSense possible for the nuget.
I manged to include *.xml and *.pdb files in the output folder into the nuget with this changes: