Contents |
A PDN is a dNAN Package file.
PDN is based on the popular ZIP file format and it is used for aggregating many files into one. A PDN file is essentially a zip file that contains a META directory. A PDN file can be created by the command-line pdn tool, or by using the dNAN.Backend.PDN API in the .NET platform. There is no restriction on the name of a PDN file, it can be any legal file name on a particular platform. PDN files are used as .NET project package. Each package is a separate project with its own development team, version number, release cycle, documentation and a defined relation to other packages (including dependencies). Packages are distributed with a description files inside at META directory, and installed on your local system using the dNAN installer.
Packages would be distributed as a Source or Binary package. See a pdn directory tree sample:
META/ META/MD5 META/BUILD.XML META/LICENSE META/MANIFEST.XML bin/ bin/Bar.dll src/ src/Foo/ src/Foo/Foo.cs src/Foo/AssemblyInfo.cs src/Foo/Foo.mdp src/Foo.mds src/Foo.userprefs
The following files/directories in the META directory are recognized and interpreted by the dNAN Platform to process a package:
The manifest file that is used to define extension and package related data.
NANT File
License file for this package.
List of MD5sums of files, for check package integrity. See an example:
124f6a3caea8c6dbacdbbb66a0309c61 META/BUILD.XML 98633c801d707f38dbec0d12308beecf META/MANIFEST.XML 41defb48f3162a1149a684b2bb4644d3 src/Foo/Foo.cs b61705c8bfc5ae2cc6ddb23a0c5b2c74 src/Foo/AssemblyInfo.cs b90b7f59516f5091566a361ea2cdb02f src/Foo/Foo.mdp ec0e9d0c20d2f065654302a60ba68f44 src/Foo.mds 7e90f0c1a54bcd938af2a3bc71c5ebed src/Foo.userprefs
The source code directory.
The binary directory.
© 2009 Novell, Inc. All Rights Reserved.
