Bootstrapper issues

[BillMcLean]

We have successful in using MSI Factor in a build script.

1) The bootstrapper is unable to use a dependency file other than the program files\MSIFactory\Bootstrap\Dependencies. If you have written your own dependency then you CAN NOT point at the dependency that you wrote yourself.

2) The custom icon file path is an absolute path rather than an relative path. We need to ensure that the build script works even if the project folder is moved to a different development branch.

All paths in the msifact file should be relative. If an absolute path is needed by a generated file, generate the absolute path when creating the generated file.

[Adam]

1) Did you create the xml file for the dependency? MSI Factory scans the XML files in the Dependencies directory when it is launched.

2) The help file states that it can use a relative path:

The full path and filename of an icon (.ico) file that will represent the product in the Add or Remove Programs in Control Panel. You can use a relative path in this field. The path will be relative to the location where the project (.msifact) file is saved. If you do not specify an icon, Windows will automatically assign one to the application. Sets the ARPPRODUCTICON property in the MSI database.

Have you had different results?

Adam Kapilik

[QnD]

Just to follow up on this, I ran into the same problem trying to use a relative path for the custom icon in the bootstrapper.

I looked at the bootstrap_config.xml file and noticed that everything else in there was an absolute path. It occurred to me that IRMakeBootstrap may not know the location of the .msifact file since it gets its input from bootstrap_config.xml which is in the Build Files folder so a relative path would mean nothing to it.

I put the variable $(var.ProjectFolder) at the beginning of the path to my custom icon and that solved the problem.