[Mono-devel-list] Npgsql assembly versioning
bmaurer at ximian.com
Sat Jul 30 14:03:02 EDT 2005
I noticed something the other day. We number our version of Npgsql as
1.0.5000.0 (ie, the same as the version of the .net fx) and build one
for the 1.1 and 2.0 profile. However, on Windows, Npgsql is numbered 0.7
and only one version ever gets installed.
So, it is impossible to deploy the same binary on Windows and Linux
without copying over a private Npgsql in one of the cases (or using
some .config file magic on windows).
IMHO, we should keep the assembly version of Npgsql the same as it is
upstream. If we feel it is necessary, we could use a publisher policy to
redirect old versions of Npgsql to the upstream version. I'm not sure
how we should handle the 2.0 profile. If we only compile npgsql once,
that means we can't put it in lib/mono/1.0, correct? That means that
people who expected -r:Npgsql.dll to work will get a suprise.
More information about the Mono-devel-list