In article <[email protected]>,
achandrapano <[email protected]> writes:
> The problem is I am using an EXE binary custom action. However, it seems to
> work if I place another DLL custom action right after my last EXE custom
> action and before InstallFinalize. This DLL custom action doesn't do
> anything except return ERROR_SUCCESS. But the installer seems to catch the
> "cancel" request now...is this OK?
Seems like a reasonable workaround, but it also seems odd that you
should have to do this. If you have an MSDN subscription, I would
recommend posting to the windows install forum/newsgroup to get a
response from MS officially. Or you could use one of the technical
support incidents from your MSDN subscription.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, &
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
