.NET COM Interop
Within AdminStudio there is the option to select a components settings to enable the '.NET COM Interop' which will create the registry entries upon installation on the target PC.
Does anyone know how this is set within Wise or will I have to manually extract the registry entries myself and add them into the component?
Cheers, Mike
Does anyone know how this is set within Wise or will I have to manually extract the registry entries myself and add them into the component?
Cheers, Mike
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
aogilmor
16 years ago
I am not sure what the ISS equivalent is, but when working with .NET apps in Wise I changed the project (.wsi) file to be a .NET app, and also had .NET installed on the Wise machine before creating the app. If you do that before creating your package it should generate the proper .net or com registry entries.
Posted by:
michaelnowell
16 years ago
I have the package set as .NET and the version of .NET required is installed on the packaging PC and I'm not getting any keys generated.
Do you know Wise add these keys into the wsi/msi so that I can view them under the components registry details (as AdminStudio does) or does it generate the keys upon installation?
Do you know Wise add these keys into the wsi/msi so that I can view them under the components registry details (as AdminStudio does) or does it generate the keys upon installation?
Posted by:
aogilmor
16 years ago
IIRC it generates entries in MsiAssembly and MsiAssemblyName tables.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.