There are lot of things going on in the DDF file, but here is what I think is important to understand.
* Comments in the file begin with a semi-colon
* .OPTION lines tell the MAKECAB utility what options to use when building the CAB archive
* .Set lines tell the MAKECAB utility what values to apply to certain parameters that are used when building the CAB archive
o Make sure the CabinetNameTemplate parameter is set to what the name of the WSP file will be (in the example above the MAKECAB utility will generate a CAB archive named my.wsp)
* Each content file to be added to the CAB archive is listed on a line in a space separated source-destination format
o For example, this CAB archive will contain an HTML file (my.html); the last line in the example above tells the MAKECAB utility to grab the my.html file from the file system (the source location) and place copy it to LAYOUTS/mysample/my.html in the CAB archive (the destination location)
o Double quotes can be used to define sources that contain spaces in the path or file name
o Make sure to include the solution meta-data XML file (manifest.xml) at the root of the CAB archive
The next step is to create the solution manifest file .
xmlns="http://schemas.microsoft.com/sharepoint/">
The example is a very simple solution manifest, but there are a couple of things to take away from it.
* Every solution has a GUID (globally unique identifier) that identifies uniquely
* As a general rule, every deployment file, schema,
