In InstallShield, right click on the Dll and select Properties. Under the
tabs, you can set the COM info to 'Extract COM Information'. The Extract
option didn't work for me because the tool didn't extract the coclass
information, just the type library.
[After a month with MS Tech Support] The whole selfreg problem stems from
a bug in MSI that prevents the installer from seeing the path to the
winsxs folders that the installer just created and placed the
redistributables from the msm files. It will work however if the
redistributable is installed previous to your install. I was able to set
up a custom action to run the vcredist_x86.exe file before the files were
copied to the machine, and it does work around the issue.
If you attempt this, don't use the vcredist_x86.exe from Microsoft's
website (it's an older version). Find the one with version 8.0.50727.762
of the dlls. It is usually buried within your VS2005 folders.
====================================================
Walter Williams
Software Engineer
Sawtooth Software, Inc.
http://www.sawtoothsoftware.com
----------------------------------------------------
"Do, or do not. There is no try."
<linalar@gmail.com> wrote in message
news:1175008113.714754.7520@b75g2000hsg.googlegroups.com...
On Feb 6, 2:13 am, David Lowndes <Dav...@example.invalid> wrote:
I have a COMdllcreated with VC++ 2005 Pro, which dynamically links to
MFC/CRT/ATL 8.0. I have created anmsiinstaller (both via InstallShield
and the VS2005 defaultmsiproject), and it correctly adds the
dependencies.
If the installer is run on Win2k/XP, it works correctly. However, when
the
dllis run onVista, thedllwill not selfregisterduring setup.
It doesregisterafterward if I run regsvr32 on it.
Walter,
Is it registering via regsvr32 only if you run that from an elevated
command prompt window?
I found that some of our components that were self-registering DLLs
failed onVistaas it appeared that portion of the installation (old
InstallShield) wasn't run elevated. I had to change from using
self-registration to the approved method where you let IS determine
the registry changes toregisterthe component.
Dave
Hi there! I'm having the same problem with self-registering DLLs in
Vista. You say that you "had to change from using self-registration to
the approved method where you let IS determine the registry changes to
register the component." How exactly do you do this? I'm using
Installshield 11...
Lina