Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Register Com in .Net installer
92 views
Skip to first unread message
Alto
Mar 3, 2004, 12:16:32 PM3/3/04
to
Hello,
I created a installation with the .Net setup project.
I have 2 COM objects I have to register and use, at the beginning everything
was fine the 2 dlls where configured automatically to register as
'vsdrfCOMSelfReg ', on the way, from one moment they both failed to
register, In the installation process I get error: 'Module
c:\windows\system32\Mydll.dll failed to register. HRESULT -2147024770.
contact your support personnel' .
The Errorlookup said: Error -2147024770 = 'The specified module could not be
found.'
If I use the 'vsdrfDoNotRegister' attribute the installer copy the files to
the system directory and then I can register them without any problem by
RegSvr32.
Any ideas how to solve it?
I created a installation with the .Net setup project.
I have 2 COM objects I have to register and use, at the beginning everything
was fine the 2 dlls where configured automatically to register as
'vsdrfCOMSelfReg ', on the way, from one moment they both failed to
register, In the installation process I get error: 'Module
c:\windows\system32\Mydll.dll failed to register. HRESULT -2147024770.
contact your support personnel' .
The Errorlookup said: Error -2147024770 = 'The specified module could not be
found.'
If I use the 'vsdrfDoNotRegister' attribute the installer copy the files to
the system directory and then I can register them without any problem by
RegSvr32.
Any ideas how to solve it?
Thanks, Arnon
Phil Wilson
Mar 3, 2004, 2:00:48 PM3/3/04
to
It looks like mydll.dll has a dependent DLL that isn't yet on the system when it
self-registers. Use vsdrfaCOM in the Register property - that gets the COM data
into the MSI file when you build it, and the entries are installed from there
without needing to load the DLL.
--
Phil Wilson [MVP Windows Installer]
----
"Alto" <ar...@prontomail.com> wrote in message
news:OpIXLMUA...@TK2MSFTNGP12.phx.gbl...
self-registers. Use vsdrfaCOM in the Register property - that gets the COM data
into the MSI file when you build it, and the entries are installed from there
without needing to load the DLL.
--
Phil Wilson [MVP Windows Installer]
----
"Alto" <ar...@prontomail.com> wrote in message
news:OpIXLMUA...@TK2MSFTNGP12.phx.gbl...
Alto
Mar 4, 2004, 1:35:11 AM3/4/04
to
Thank's for your help, You are probably right , each one of them need the
other and at list another component.
I tried to use the vsdrfaCOM property but I got warning: "WARNING: Unable to
create registration information for file named 'IEBackGroundClener.dll'' at
the building of the project.
A work around that is work for me for now is a VB script that register the
dlls at the end of the installation.
other and at list another component.
I tried to use the vsdrfaCOM property but I got warning: "WARNING: Unable to
create registration information for file named 'IEBackGroundClener.dll'' at
the building of the project.
A work around that is work for me for now is a VB script that register the
dlls at the end of the installation.
Arnon
"Phil Wilson" <phil....@unisys.spamcom> wrote in message
news:#MVRYHVA...@tk2msftngp13.phx.gbl...
Alto
Mar 4, 2004, 2:31:23 AM3/4/04
to
Sorry, correction to my previous post, The vb script also doesn't work some
of the times.
Is there a way to tell the installer the sequence of the actions so I could
register only after all the necessary files where copied?
of the times.
Is there a way to tell the installer the sequence of the actions so I could
register only after all the necessary files where copied?
Arnon
"Alto" <ar...@prontomail.com> wrote in message
news:#9oTcKbA...@tk2msftngp13.phx.gbl...
Phil Wilson
Mar 4, 2004, 12:58:42 PM3/4/04
to
That still looks like a dependency problem of some sort. VS will load the DLL
and call DllRegisterServer and try to capture the created registry entries. It
should be able to do that on your build machine as long as your DLL can load and
find it's dependendent DLLs. If it's C++ built with VS .NET, you *might* have
dependencies that you're not aware of - msvcrt70.dll, mfc70.dll, atl70.dll as
well as any of your own DLLs it links to.news:%239oTcKb...@tk2msftngp13.phx.gbl...
and call DllRegisterServer and try to capture the created registry entries. It
should be able to do that on your build machine as long as your DLL can load and
find it's dependendent DLLs. If it's C++ built with VS .NET, you *might* have
dependencies that you're not aware of - msvcrt70.dll, mfc70.dll, atl70.dll as
well as any of your own DLLs it links to.news:%239oTcKb...@tk2msftngp13.phx.gbl...
0 new messages