On Fri, Jun 17, 2011 at 12:08 AM, Markus Schaber <[email protected]> wrote: > Ok. But at least you should update the FileVersion then, or give some > other visible indicator that allows at least manual diagnostics which > version actually is installed.
Oh, of course! Only AssemblyVersion will remain the same. > >> I figure if MS can do it with the .NET service packs, then we can too. > :) > > .NET service packs run a lower risc of being downgraded silently by an > installer unconditionally writing the old version into the GAC. :-( Only the IronPython installer should be adding them to get GAC. I'll check to make sure that you can't install 2.7 over 2.7.1 (it should bail with a "cannot downgrade" message, but getting installers right for these scenarios is hard :|). > > Maybe the version overriding via manifest or .conf files would work? Yeah, binding redirects are an option, but they're horribly ugly. This is the same path taken with the IronPython 2.6 series - their version numbers remained the same throughout, and we didn't get any complaints that I recall. Worst case, if there are major issues, I'll spin a 2.7.2 with a new version, but I'm expecting anything. - Jeff _______________________________________________ Ironpython-users mailing list [email protected] http://mail.python.org/mailman/listinfo/ironpython-users
