Hi, You cannot change the Product Name in through the command line. You can use Transform but it is not such dynamic as you want. Using transforms requires all transforms to be created before launcjing the installation.
On Tue, Feb 3, 2015 at 11:43 PM, <wix-users-requ...@lists.sourceforge.net> wrote: > Send WiX-users mailing list submissions to > wix-users@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/wix-users > or, via email, send a message with subject or body 'help' to > wix-users-requ...@lists.sourceforge.net > > You can reach the person managing the list at > wix-users-ow...@lists.sourceforge.net > > > Changing the Product Name at install (Brian Enderle) > > > From: Brian Enderle <bria...@gmail.com> > To: WiX Users <wix-users@lists.sourceforge.net> > Cc: > Date: Tue, 3 Feb 2015 11:00:08 -0500 > Subject: [WiX-users] Changing the Product Name at install > We have a generic solution that is customized via a settings file to make a > unique product. We license all of our products and part of the license > check is to make sure the product name embedded in the license key matches > the unique product's product name like so: > > // Check license against product name > Assembly assembly = Assembly.GetEntryAssembly(); > FileVersionInfo fvi = > FileVersionInfo.GetVersionInfo(assembly.Location); > if (fvi.ProductName != this.LicensedProduct) > this.LicenseStatus = LicenseStatusOptions.InvalidLicense; > > In the past we would fork the generic solution and create a new project so > that the product name could be changed. I would like to know if there is a > way to change the product name at the time of install so that I could have > just one generic project with a unique installer for each new product and > still allow unique licensing between each unique product. > > I tried setting <Product Name="My First Product"> but that didn't change > the fvi.ProductName. > > I also have tried MSBuildTasks but this rewrites the original generic > AssemblyInfo.cs file which I don't want to do. > > > In case the above is not clear, here is an example: > > I have GenericProduct.exe with a ProductName of 'Generic Product' (as > defined in the AssemblyInfo.cs file, i.e. [assembly: > AssemblyProduct("Generic Product")]) > > I create two new installer projects named MyFirstProduct and > MySecondProduct. > > When I install MyFirstProduct I need fvi.ProductName (from code snippet > above) to be 'My First Product' so that the license key for My First > Product works with My First Product and NOT with My Second Product. > > Brian > > If you can't explain it simply, you don't understand it well enough. - > Albert Einstein > > > > -- Regards, Fyodor Koryazhkin.. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
