> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Sigurd Stenersen
> Sent: Monday, October 02, 2006 6:22 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Installing machine-specific license files
>
Arnette, Bill wrote:
> the [...] system will package the .msi up
> in a self-extracting zip file for the user to download.
Why ?
Sigurd
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsa
Arnette, Bill wrote:
RE: [WiX-users] Installing machine-specific license files
Actually, I was thinking I could use the same
product code, upgrade code, and component ids for each customized
license file installer. I don't think this will be a problem. Am I
missing some
Title: RE: [WiX-users] Installing machine-specific license files
Actually, I was thinking I could use the same product code, upgrade code, and component ids for each customized license file installer. I don't think this will be a problem. Am I missing something?
-Original Me
Arnette, Bill wrote:
> So my plan is to create a WiX project that the licensing system builds
> whenever it gets a license request. The licensing system will generate
> the license files and then build the WiX project.
> I'll create a WixLib with the components for the license files. After
> the
Our licensing system is similar to Windows Product Activation in that a
hash is created for the machine the software is licensed on, sent to us,
and we return a self-extracting executable that installs a bunch of
license files that are generated for that specific machine. What this
means is that
6 matches
Mail list logo
