|
None
of the "old" CA's worked from an installation (but work when called from a
'normal' application). I've continued to test and found out that the
'Release'build works but not the 'Debug'build, so I believe there's something
about my debug-stuff that mess things up.
My
guess is that the 'MSI46.tmp'-file is the DLL, and then it should be +280kb
...
/Jonas
Jonas Jonsson L (AL/EAB) wrote:
The DLL (and the
new functionality) has of course been tested (on W2K & W2K3s) outside of
an installation, and works just as expected, but when I try to access ANY
functionality in the DLL, I get an Error 1723 and the installation
fails. Do the other CA functions still
work? If so, I'd start with the basics: making sure the new function is
exported, has the right signature, etc. Then add a MessageBox or logging as
the first thing in the function so you know whether it's starting at all.
Is there
anything special with regards to using netapi32.lib in installations (I'm
using the NetLocalGroupAdd()-function)?
There shouldn't be any.
The DLL is just
as usual in the Binary table of the msi-file. In the line above (from
the install.log-file), the library referenced
(C:\WINNT\Installer\MSI46.tmp), has the size of 5112 bytes on disk during
execution of the installation. What's the purpose of that file?
MSI extracts the DLL from the Binary
table to a secure location before running it. Is that the expected size?
--
sig://boB
http://bobs.org
|
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
