There are a lot of reasons not to use script based custom actions due to
environmental issues. They have a tendency to fail significantly more often
than other types of custom actions (and custom actions have a tendency to
fail significantly more than the built in support).
Personally, I recommend
Thanks, I found that and fixed a few other VBScript problems and now I
have it working. (Only to discover other problems, however.)
Scott
On Mon, Nov 2, 2009 at 1:15 PM, Wilson, Phil wrote:
> The WScript.Echo won't work - that's supplied by the WSH object, not by MSI.
> Do you see that message?
The WScript.Echo won't work - that's supplied by the WSH object, not by MSI. Do
you see that message?
MsiProvideComponent is normal - any of the entrypoints that have a Darwin
descriptor (COM,file associations, shortcuts) use that to locate the target
file (causing repair if needed).
Apart f
3 matches
Mail list logo