We had the same issue when our major version number went above 255. In this case I made a string with the text "260.1.0" and showed this to user on all the dialogs and in the product name, but internally the MSI is version 2.60.1.0. You may have to get a bit creative with the Upgrade table to handle updates properly from earlier versions that are now actually a higher version number.
Rob On 27/08/2010 15:51, Sohail Somani wrote: > Hi, > > I'm currently in the middle (or nearing the end, I hope) of porting an > installer from the evil that shall not be named to WiX. > > Mostly, it's been pretty easy. However, one thing which is sticking out > is the version number. The products being ported use the current year as > the major version number and this means strings like "2011.foo.bar". > > Obviously, if I try to use such a version, I am greeted with CNDL0242. I > did find a workaround at the following page: > > http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg38954.html > > But that seems like it is guaranteed to cause me problems. Is there a > simpler way to exceed the limits without using VB script? Should I write > to the registry manually? > > Thanks. > ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
