Brett,
Review the links I gave earlier.
You can use the "Register User User Interface Dialog" and/or the "Customer
Information User Interface Dialog" to allow the user to either display a
separate program (or web site) to register the program. It sounds like you
want the Customer Information dialog, to allow the user to enter a serial
number (aka unlock code) that the setup program then checks. Note the setup
program by default only checks if the serial number matches the
SerialNumberTemplate on the Customer Information, you need to use other code
to ensure it matches a specific number. For further details on the Serial
Number see the Windows Installer SDK itself.
http://msdn.microsoft.com/library/d...customerinformationuserinterfacedialogbox.asp
http://msdn.microsoft.com/library/d...o7/html/vxgrfserialnumbertemplateproperty.asp
http://support.microsoft.com/default.aspx?scid=kb;en-us;253683
http://msdn.microsoft.com/library/d...us/msi/setup/windows_installer_start_page.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/property_reference.asp
Unfortunately I don't have a good link to a sample leveraging the Customer
Information dialog...
Hope this helps
Jay
|I see now.
|
| Will the install allow some other type of switch like the EUL? For
example,
| an application unlock code. If the code they have matches, it installs,
if
| not, it doesn't install.
|
| Thanks,
| Brett
|
| | > Brett,
| > | Yes - you are correct and that value (agree or not) must be stored
some
| > | where so the app will not continue nagging you with the EUL. The app
| > itself
| > No that value (agree or not) does not need to be stored! As the presence
| > of
| > the executables (EXE & DLL) is the answer to if they agreed or not! If
the
| > executables are on their hard drive, they agreed. If the executables are
| > not
| > on their hard drive they did not agree!
| >
| >
| > Am I just making this too simple for you? Or am I missing something?
| >
| >
| > You want to write a Installation program (a setup program). Correct?
| >
| > You want to the setup program to display a License Agreement. Correct?
| >
| > Based on your original post, <quote>Say I want my installation to popup
a
| > user agreement, after they select yes, the install continues. </quote>,
| > the
| > above two questions are what you want. The VS.NET Setup Project (as I
| > suggested in my other post) automatically does this.
| >
| > If the user accepts the License Agreement, on the License Agreement
| > Dialog,
| > the setup program will install your program.
| > If the user declines the License Agreement, on the License Agreement
| > Dialog,
| > the setup program will not install your program.
| >
| > No need to store the answer, as the answer controls whether the programs
| > are
| > installed or not.
| >
| > The only "problem" might be if your app supports X-Copy installation,
and
| > they know where to find a copy of the executables...
| >
| > Hope this helps
| > Jay
| >
| >
| >
| >
| >
| >
| > | > |
| > message
| > | | > | > Brett,
| > | > So was I! ;-)
| > | >
| > | > If they agree the app will be installed.
| > | >
| > | > If they don't agree the app will not be installed.
| > | >
| > | > Ergo: The fact the app is installed & executing tells you if they
| > agreed
| > | > or
| > | > not.
| > |
| > | Yes - you are correct and that value (agree or not) must be stored
some
| > | where so the app will not continue nagging you with the EUL. The app
| > itself
| > | has no way to store the selection (yes/no) because it is all compiled
| > code.
| > | Simpliest case is to store it in a TXT file. However, if some one
| > modifies
| > | that file, the EUL screen appears again. This is a simple example but
| > | applies to something like an application code (was it the right code
or
| > | not). I don't want people modifying the file but am not sure how to
| > stop
| > | them.
| > |
| > | >
| > | > Hope this helps
| > | > Jay
| > | >
| > <<snip>>
| >
| >
|
|
