Acumatica.nuspec

<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id>Acumatica.PX.Main</id>
        <version>22.100.178</version>
        <description>Acumatica PX common main libraries</description>
        <authors>Aktion Associates</authors>
        <references>
		<reference file="PX.Common.dll" />
		<reference file="PX.Common.Std.dll" />
		<reference file="PX.CS.Contracts.dll" />
		<reference file="PX.Data.dll" />
		<reference file="PX.Data.BQL.Fluent.dll" />
		<reference file="PX.Objects.dll" />
        </references>        
    </metadata>
    <files>
	  <file src="PX.Common.dll" target="lib\" />
	  <file src="PX.Common.Std.dll" target="lib\" />
	  <file src="PX.CS.Contracts.dll" target="lib\" />
	  <file src="PX.Data.dll" target="lib\" />
	  <file src="PX.Data.BQL.Fluent.dll" target="lib\" />
	  <file src="PX.Objects.dll" target="lib\" />
    </files>
</package>

A NuGet package manifest is created by defining the contents in a .nuspec XML file. The schema for a .nuspec file can be found within its documentation at https://docs.microsoft.com/en-us/nuget/reference/nuspec. This XML shows an example of the contents of a .nuspec file (e.g. Acumatica.nuspec) for the Acumatica libraries listed.

Within this XML, the package is supplied a name (< id >) and a version (< version >), the files to reference in the destination Visual Studio project (< references >), and the source files to include in the package (< files >). Notice in this example that I’m naming the package Acumatica.PX.Main, and I’m including Acumatica build version 22.100.178 of its libraries.