Thank you,
--
Vlad Hrybok
http://UltiDev.com
It's relatively harmless in itself, except that the reason the code did not
release the handle could be that it crashed.
--
Phil Wilson
[MVP Windows Installer]
"Vlad Hrybok" <vgr...@newsgroups.nospam> wrote in message
news:2354506E-B995-468A...@microsoft.com...
The installer is generated by Visual Studio 2005 Setup project, meaning that
I do not manually open or close MSIHANDLEs - Installer class of .NET
Framework, I think, does it. My customer can't get my product installed and
this is the only message they get in the MSI log. It looks like MSIHANDLE
error is not the root cause. Do you have an idea why .NET Installer class
would cause this issue?
--
Vlad Hrybok
http://UltiDev.com
"Vlad Hrybok" <vgr...@newsgroups.nospam> wrote in message
news:62305789-C0EE-4817...@microsoft.com...
"Vlad Hrybok" <vgr...@newsgroups.nospam> wrote in message
news:01A57681-BAED-49D0...@microsoft.com...