This issue has been fixed in Wise Installation Studio/Express 7 SP1. The fix for this issue will also be included with the next release of Wise Package Studio.
There are several possible workarounds for this issue:
- If you want the Assembly type to be None for all files, compile the .wsi on a computer that does not have .NET Framework installed.
- If you want the Assembly type to be None for a specific file, open the .msi in Orca and remove the entry for the appropriate file from the MsiAssembly table.
- Create a macro that removes entries found in the MsiAssembly table that have no corresponding entry in the MsiAssemblyName table. A sample VBScript that performs this task can be found attached to this article. You may need to modify this VBScript based on your needs. This VBScript should be run on the .MSI after each compile. To run the VBScript use the command <path to MsiAssemblyFix> "<Path to .MSI>".
- Running Caspol.exe from the commandline on the machine that is running Windows Installer Editor may correct this issue. Caspol.exe is a tool available from Microsoft's MSDN.
The required command:
"C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CasPol.exe" -m -ag 1.2 -url file://NetworkMachine/FolderContainingDotNetAssemblies/* FullTrust
For further information on Caspol.exe and how to use the Caspol.exe tool, please see the attached link.
Wise Installation Studio 7