Heat works well for self-registered DLLs; is there a similar technique
that one can use for the results of RegAsm / RegTlib on a .NET assembly
/ type library? Is there a way to get a child process to inherit the
Registry re-mappings? The same thing would be useful for
self-registered EXEs.
Well, RegAsm has the /regfile switch, but it doesn't work with the /tlb
option; RegTLib has no such switch; I suppose I could embark on the
wonderful world of code injection (which I'm sure my virus scanner will
love), but even with CreateRemoteThread it looks pretty nasty. I recall
how
Heat can capture quite a lot but not self-reg exes. I have also used
something called RegSpy but I can't remember where it came from.
Neil
-Original Message-
From: Thomas S. Trias [mailto:tomtr...@artizan.com]
Sent: 03 March 2009 19:31
To: 'General discussion for Windows Installer XML
These should still work for self-registering exes, here:
http://installsite.org/pages/en/msi/tips.htm
Scroll down to RegSpy. It indeed uses CreateRemoteThread and
RegOverridePredefKey. Somebody also extended it to do tlbs, RegSpy2. The
source is all there. The original magazine article is
4 matches
Mail list logo
