|
Yes, I do know I can use whatever name I like to (including the default "SQL Anywhere 12 Deployment"), but what exactly is the desired handling? Am I supposed to use a customized name (such as "MyCompany SQL Anywhere 12 Deployment"), does it depend on whether I'm deploying an OEM version, whether I'm about to install in the default path or a customized one, or are there different reasons? Just would like to get the idea behind this:) [And yes, I do know that the generated Product Code is not the official code for the SQL Anywhere product and as such, won't enable the usage of an EBF. But that is another (and already answered) question.] |
|
The name you enter here is what shows up in the list of installed programs in the Control Panel. As you suggest, it can be whatever you like, but preferably it would be something that is unique and that identifies your product, such as "SQL Anywhere 12 for My App". If you install two deployment wizard installs with the same name, only one will be listed in Add/Remove programs. By the way, the Product Code is the GUID that uniquely defines the install. If you are preparing an update to a previous deployment of SA, use the same GUID again and the generated MSI will upgrade the existing installation when it is run. |
