[cvsnt] Latest updates

[Tony Hoyle]

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