> If your custom action could talk to the server, why not just make your > application generate a machine unique id and ask the server for the > information. Or you could do that from the installation.
Because then the server would not know which user this is. > If you just want to gather an id you can use a UI page to do that or pass a > parameter to the MSI if you have no UI. When you have this information in a > property you can do many things with it. For example use it as a service > parameter. I could ask the user for the information, but the point of this is to avoid asking the user for anything at all.. I'll explain in detail: 1. The user logs on his profile online (with an internet browser) 2. When the user initiates the download the installer is somehow imprinted with an unique identifier (filename or something else..) 3. A custom action application is run with the identifier as an argument 4. The custom action request the users credentials from a server with the identifier as an argument 5. The user gains access to the service The goal here is to give the user access to the service online after installing the necessary client -without- the user having to provide credentials manually. The credentials are already provided by logging in to the website. Make sense? - Jorn ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
