Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Tony, > Try CVSNT_INSTALLDIR. OK, I did: msiexec /i cvsnt-2.0.60.msi SERVER=0 CVSNT_INSTALLDIR="C:\Program Files\GNU\WinCvs 1.3\cvsnt" It displays the location in the installer correctly, but then it installs into "C:\Program Files\cvsnt" anyway. In fact it installs in the same place even if I manually set the location using the browse key, no matter whether the CVSNT_INSTALLDIR is used or not and no matter what folder I choose. > The product code is unique to the build (randomly generated > automatically by wix).. I need some simple way tu uninstall CVSNT when uninstalling WinCvs, any ideas? I also noticed that installer grew in size from 2,257,157 bytes for cvsnt-2.0.51d.exe to 3,252,736 bytes for cvsnt-2.0.60.msi. From the log comments I am guessing that we are back to distributing the MFC dlls instead of static linking. Is there any particular reason for that? Overall new installer doesn't make good impression on me and seems to create problems with some basic operations. Not sure I would recommend anything like that to use in corporate environment. Maybe it's better to just launch Innosetup installers from within master MSI installer - it will give the impression of MSI to any dumb administrator that requires it and allow to use Innosetup at the same time. Best Regards, Jerzy ----- Original Message ----- From: "Tony Hoyle" <tmh at nodomain.org> Newsgroups: support.cvsnt To: <cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook> Sent: Wednesday, November 10, 2004 1:44 Subject: Re: [cvsnt] Latest updates > Jerzy Kaczorowski wrote: > > 1. I would like to control the install location, which seems to be often > > arranged with INSTALLDIR or TARGETDIR property > > > Try CVSNT_INSTALLDIR. > > > 2. When trying to uninstall CVSNT while uninstalling WinCvs, what would be > > the product code to be used with msiexec /x command (the msi installer is no > > longer around and can't be used so I'm guessing we need a product code > > instead). > > The product code is unique to the build (randomly generated > automatically by wix).. only the upgrade code stays the same, but I've > no idea where that is stored or how it is used. Presumably there's a > way of invoking add/remove programs directly somehow. > > Tony > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs >