I have used the following website to get my guidance package setup file.

http://adrianalonso.blogspot.com/2007/06/sft-setup-project-deploying-many.html

It creates a WiX setup project for me, but that setup project does not include any custom referenced assemblies by my Guidance package. There are several files that are created by the SFT WiX setup, but I do not know where I have to go and add all the custom assemblies that are required by the Guidance package.

The custom assemblies are from the Data Access Guidance Package that I used as a template to generate CRUD sp. My Guidance package is a hybrid of HOL, Data Access Guidance Package and SFT. It all works fine on my machine. To clear things up this is what I have:

• IvyIrisPackage (Guidance Package)
• Extensions (Custom Assembly)
• ScehmaDiscovery (Custom Assembly)
• SoftwareFactories.ServiceFactory (Custom Assembly)

From the SFT setup the only dll that gets installed is "IvyIrisPackage.dll". I don't know if I just need to add the other custom asseblies in the ".wxs" file.

Any help would be appreciated.

Thanks,

Gaurav Bhasin

Hi Gaurav, after creating the SFT Setup Project you should have a $GuidancePackageName$Setup.wxs file which contains the main setup definition for your guidance package. In your case the filename should be “IvyIrisPackageSetup.wxs�

After opening the file you should have something like this:

<Fragment Id='GatGuidancePackage1'>

�/span>

<DirectoryRef Id='INSTALLDIR'>

<Directory Id="IvyIrisPackageDirectory"

Name="GPD" LongName="IvyIrisPackage" >

<Component Id='IvyIrisPackageComponent'

Guid='687acc27-1320-4940-bb85-4c585f54cbb4'>

<File Id='IvyIrisPackageAssembly'

Name="GPCK.dll"LongName="IvyIrisPackage.dll"

src='$(var.IvyIrisPackage.Build.Dir)IvyIrisPackage.dll'

DiskId='1' Vital='yes' />

<File Id='IvyIrisPackageXML'

Name="GPCK.xml" LongName="IvyIrisPackage.xml"

src='$(var.IvyIrisPackage.Build.Dir)IvyIrisPackage.xml'

DiskId='1' Vital='yes' />

</Component>

</Directory>

</DirectoryRef>

�/p>

</Fragment>

Basically what you will need to do is to add a file element for each custom assembly. For example, if you want to add a custom assembly named SchemaDiscovery.dll located in the guidance package output build directory you will have to add the following file element:

<File Id='IvyIrisPackageSchemaDiscovery'

Name="SD.xml" LongName="SchemaDiscoverry.dll"

src='$(var.IvyIrisPackage.Build.Dir)SchemaDiscoverry.dll '

DiskId='1' Vital='yes' />

You should not change the Vital and DiskId attributes.

As this is a very common scenario, this behavior will be probably included in the next release of SFT so you won’t need to change (and know how to) WIX files manually anymore

Hi Gaurav, after creating the SFT Setup Project you should have a $GuidancePackageName$Setup.wxs file which contains the main setup definition for your guidance package. In your case the filename should be “IvyIrisPackageSetup.wxs�

After opening the file you should have something like this:

<Fragment Id='GatGuidancePackage1'>

�/span>

<DirectoryRef Id='INSTALLDIR'>

<Directory Id="IvyIrisPackageDirectory"

Name="GPD" LongName="IvyIrisPackage" >

<Component Id='IvyIrisPackageComponent'

Guid='687acc27-1320-4940-bb85-4c585f54cbb4'>

<File Id='IvyIrisPackageAssembly'

Name="GPCK.dll"LongName="IvyIrisPackage.dll"

src='$(var.IvyIrisPackage.Build.Dir)IvyIrisPackage.dll'

DiskId='1' Vital='yes' />

<File Id='IvyIrisPackageXML'

Name="GPCK.xml" LongName="IvyIrisPackage.xml"

src='$(var.IvyIrisPackage.Build.Dir)IvyIrisPackage.xml'

DiskId='1' Vital='yes' />

</Component>

</Directory>

</DirectoryRef>

�/p>

</Fragment>

Basically what you will need to do is to add a file element for each custom assembly. For example, if you want to add a custom assembly named SchemaDiscovery.dll located in the guidance package output build directory you will have to add the following file element:

<File Id='IvyIrisPackageSchemaDiscovery'

Name="SD.xml" LongName="SchemaDiscoverry.dll"

src='$(var.IvyIrisPackage.Build.Dir)SchemaDiscoverry.dll '

DiskId='1' Vital='yes' />

You should not change the Vital and DiskId attributes.

As this is a very common scenario, this behavior will be probably included in the next release of SFT so you won’t need to change (and know how to) WIX files manually anymore