Switch View

Community Content

In this section

Statistics Annotations (17)

Click here to expand

Language Filter

This page is specific to

The 2007 product release

Other versions are also available for the following:

The 2010 product release

Solution Schema

A solution manifest file defines the constituent parts of a solution, including its files, assemblies, code access security, Web Parts, Features, site definitions, and other resources.

Solution

ApplicationResourceFiles

ApplicationResourceFile

SiteDefinitionManifests

SiteDefinitionManifest

WebTempFile

TemplateFiles

TemplateFile

Example

The following example shows a solution manifest file that includes declarations for Features, site definition files, and assemblies.

Xml

<Solution SolutionId="4AFC1350-F354-4439-B941-51377E845F2B" 
  xmlns="http://schemas.microsoft.com/sharepoint/">
  <FeatureManifests>
    <FeatureManifest Location="Calls\feature.xml"/>
    <FeatureManifest Location="ServiceRequest\feature.xml"/>
    <FeatureManifest Location="Customers\feature.xml"/>
    <FeatureManifest Location="HelpDeskCore\feature.xml"/>
  </FeatureManifests>
  <TemplateFiles>
    <TemplateFile Location="Mobile\HelpDeskHomePage.ascx"/>
    <TemplateFile Location="1033\xml\webtemphd.xml"/>
    <TemplateFile Location="SiteTemplates\HelpDesk\onet.xml"/>
    <TemplateFile Location="SiteTemplates\HelpDesk\default.aspx"/>
  </TemplateFiles>
  <Assemblies>
    <Assembly DeploymentTarget="GlobalAssemblyCache"
      Location="HelpDeskCoreFeatureReceiver.dll"/>
    <Assembly DeploymentTarget="WebApplication"
      Location="ServiceRequestValidation.dll"/>
  </Assemblies>
</Solution>

The following example shows a manifest for a solution that includes two Features, a single site definition manifest, and a single resource.

Xml

<Solution SolutionId="7AFC4320-F354-6439-B745-77387E847F2H" 
  xmlns="http://schemas.microsoft.com/sharepoint/">
  <FeatureManifests>
    <FeatureManifest Location="MyFeature\feature.xml"/>
    <FeatureManifest Location="OtherFeature\otherfeat.xml"/>
  </FeatureManifests>
  <SiteDefinitionManifests>
    <SiteDefinitionManifest Location="STS">
      <WebTempFile Location="1033\STS\webtempSTS.xml"/>
    </SiteDefinitionManifest>
  </SiteDefinitionManifests>
  <Resources>
    <Resource Location="FeatureName\Resources.ja-ja.resx"/>
  </Resources>
</Solution>

Tags

: Add a tag

Community Content

Add new content

Annotations

Sample for RootFile and ApplicationResourceFile

mattgl | Edit | Show History

If you haven't found out by trying, here is what I found out:

Files which are specified under ApplicationResourceFile like so:

<ApplicationResourceFiles>
<ApplicationResourceFile Location="MyFiles\My.resx" />
</ApplicationResourceFile>

a) have to be located in a MyFiles folder within the .wsp cabinet and

b) will be deployed to a directory relative to the Virtual Server root directory, i.e. to C:\Inetpub\wwwroot\wss\VirtualDirectories\80\resources\MyFiles

Your .ddf for the cab file creation file would look like this:

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
.OPTION Explicit ; Generate errors
.Set CabinetNameTemplate=TestResources.wsp
.Set DiskDirectoryTemplate=CDROM
.Set CompressionType=MSZIP
.Set UniqueFiles=Off
.Set Cabinet=On
.Set DiskDirectory1=.

manifest.xml

.Set DestinationDir=MyFiles
My.resx

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

In order to deploy files to the C:\...\12\Resources folder (or to any other folder beneath the 12 hive), you need to use the RootFile element like so:

In this case, you also have to assure that the folder ein your .wsp cabinet is the same folder which will be the relative folder in relation to the 12 folder.

Your .ddf for the cab file creation file would look like this:

.Set DestinationDir=Resources
Test.resx
Test.de-de.resx

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;