This is the kind of thing you'd do:
http://support.microsoft.com/kb/253683/en-us
where it sets the PIDCHECK property to denote that the key is valid. The rest
of the article is about how to use the custom action from Visual Studio setups
using Orca, and that can be ignored.
Phil Wilson
From: Eric Latendresse [mailto:[EMAIL PROTECTED]
Sent: Monday, March 10, 2008 3:50 PM
To: Wilson, Phil; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Validate Product Key Dialog with custom action
Thanks for your reply Phil. I did find some examples on managed custom actions
and I know what you mean by "arm-weaving". I also found an example using a C++
Win32 application. This seems like it is the way I need to go but the example
was outdated and the code didn't compile. I'm not very familiar with C++, do
you have an example that I could follow?
Thanks,
Eric
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wilson, Phil
Sent: Monday, March 10, 2008 5:39 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Validate Product Key Dialog with custom action
You can't get there from here. The infrastructure for calling managed code
custom actions isn't natively supported by MSI, and even if you did all the
arm-waving to make it work as a custom action (called from the UI sequence)
it's so decoupled from the install that you cannot use it to set a property in
the install. This is important because you probably need to disable the next
button until the key is valid, and this mechanism uses properties.
When I say "arm waving" I don't mean the InstallUtilLib.dll stuff, bad as it
is, I assume that you are in the UI sequence and no files have been installed.
How do you get your assembly onto the system, and how do you call it? This is a
mountain of code.
Speaking of mountains, there's a mountain of opinion in the archives and
elsewhere on calling managed code custom actions, most of which falls into two
categories : 1) "Don't do it because of the issues involved" and 2) "Why the
heck doesn't WiX/MSI support it". So if all you're going to do is look at the
text of the key and say Yes or No, then vbscript isn't too bad. If you're going
out into the world to read files or the internet, C++ is recommended.
Phil Wilson
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Latendresse
Sent: Monday, March 10, 2008 10:33 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Validate Product Key Dialog with custom action
I want to use a C#.net assembly to validate my product key. Could someone point
me in the right direction on where to start?
Thanks,
Eric
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
