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 firstname.lastname@example.org.
Tony, > Odd. works for me. Odd is what you get when using MSI, I guess ;) > I was getting linker errors because you can't mix static/dynamic. The > difference in size is minor, really. I don't see how nearly 1MB difference (increase by 50% from 2M to 3M) is a minor difference. Additionally I don't like installers to screw up my dlls, and in case of MSI (which is not only buggy but also both stupid and ugly) it means that the latest CVSNT is not allowed on my work PC. > Unfortunately it's pretty much essential now. You can't even get a foot > in the door without an MSI installer. Don't know about that, but normally the installer is not a major factor for a company deciding to use a system. How about creating two versions: the 'professional' (with MSI) and 'popular' (Innosetup)? While we are at it - I would really like to also have a client-only installer which contains cvs.exe that doesn't have the server-specific code in it. It should be much smaller that way and I think it would not have MFC dependency since most of MFC is involved in server support code I guess. On another note - latest cvs.exe is crashing on me like hell, can't get it to even display version or anything. No problem with 51d or any other previous version. 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: Thursday, November 11, 2004 0:31 Subject: Re: [cvsnt] Latest updates > Jerzy Kaczorowski wrote: > > 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. > > Odd. works for me. > > > I need some simple way tu uninstall CVSNT when uninstalling WinCvs, any > > ideas? > > I'm not sure that's possible, other than making WinCvs an MSI too and > having a combined installer. > > > 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? > > I was getting linker errors because you can't mix static/dynamic. The > difference in size is minor, really. In theory I could start building > msps which would be tiny if required, but probably won't bother... 3MB > is hardly a lot nowadays. > > > 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 > > Unfortunately it's pretty much essential now. You can't even get a foot > in the door without an MSI installer. > > > 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. > > Won't work - you need to be able to control the install from active > directory - eg. automatically installing to a fixed directory on an > entire forest, network based 'install on first use' installs, etc. > Innosetup just can't do that... it doesn't have the options. > > 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