Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>To extract the COM information, tallow will use the <a href="http://msdn.microsoft.com/en-us/library/tzat5yw6(VS.71).aspx" rel="nofollow noreferrer">regasm.exe tool</a> included with the .NET framework. It is likely that visual studio uses the same tool to register assemblies when you enable "register for COM interop". </p> <p>The difference is that tallow will use the regasm /regfile switch to send the information to a .reg file instead of actually registering the assembly. Unfortunately the .reg file generated by regasm.exe is not complete. It skips the typelib entries which it does write to the registry during a real registration. This may be a bug in regasm.</p> <p>To get your installer working you have three options:</p> <ol> <li><p>Add the missing registry keys to the tallow output manually. The tallow output is intended to be edited manually and saved along with your other wxs files anyway. You seem to be trying to fully automatically generate a working wxs file but I believe that was never a design goal of tallow.</p></li> <li><p>Use a <a href="http://wix.sourceforge.net/manual-wix2/wix_xsd_customaction.htm" rel="nofollow noreferrer">custom action</a> to invoke regasm from your installer. This is slightly evil because you may lose some of the strong transactional guarantees provided by the windows installer engine. I'm thinking of rollbacks triggered by a failure halfway during the install here.</p></li> <li><p>Avoid the registration altogether by making use of <a href="http://msdn.microsoft.com/en-us/library/ms973915.aspx" rel="nofollow noreferrer">registration-free COM.</a> This will require the creation of manifest files for both the application and the COM library.</p></li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload