Why do I need to check the version myself?

[D. Yates]

Hi,

I got bit by the fact that applications using library files that are NOT
strongly named will use older versions of the library without generating an
error, so........

Is there a way to tell an application "Use the library files you were built
with or NEWER versions" without using the GAC?

I have tried giving my library files strong names, but that locks them to
ONE version of the library file. I know that you can add lines to your
application configuration file to tell the application to use a specific
version of a new file (i.e. if you using version 1.2.0.0- 1.2.3.0 now use
1.2.4.0). However, it doesn't allow me to specifiy "USE ALL newer versions"
(e.g. if you using version 1.2.0.0- 1.2.3.0 now use 1.2.*). I have to target
ONE newer version, which means EVERY time I have an update, I would have to
update every applications configuration file with new routing information.

I can use this code at runtime to fix the problem, but I'm look for other
options:

public static bool IsOkToUseLibrar ies(string sDirectory, string
sLibStartsWith,
Assembly asm, out string sProblem)
{
string sFileName;
sProblem = string.Empty;

foreach (AssemblyName asname in asm.GetReferenc edAssemblies())
{
if (asname.Name.St artsWith(sLibSt artsWith))
{
sFileName = sDirectory + "\\" + asname.Name + ".dll";
if (System.IO.File .Exists(sFileNa me))
{
System.Diagnost ics.FileVersion Info fvi =
System.Diagnost ics.FileVersion Info.GetVersion Info(sFileName) ;

// major.minor[.build[.revision]]
if ((fvi.FileMajor Part != asname.Version. Major))
{
sProblem = string.Format(" {0}.dll -> System {1} file " +
"found by a system {2} application.\n" , asname.Name,
fvi.FileMajorPa rt, asname.Version. Major);
}
else if ((fvi.FileMinor Part < asname.Version. Minor) ||
(fvi.FileBuildP art < asname.Version. Build) ||
(fvi.FilePrivat ePart < asname.Version. Revision))
{
sProblem = string.Format(" {0}.dll -> Expecting a " +
"version number greater than or equal to {1}, but found
{2}.\n",
asname.Name, asname.Version. ToString(), fvi.FileVersion );
}
}
}
}

return (sProblem == string.Empty);
}
Thanks for any suggestions,
Dave

[Andy]

The behavior you describe is by design. The reason the app will use
the old version of the library is because the newer version's behavior
may not be compatiable with the older version. This is the cause of
many problems in the COM base world.

That said, you can specify using the application configuration file to
use newever versions of assemblies. Look up the bindingRedirect method
of the configuration file, that will give you information to force a
newer version of the library. Of course you would only want to do this
after you've tested your application against the newer version of the
library.

HTH
Andy

[D. Yates]

Andy,

Thanks for your response. I have looked at the bindingRedirect , but I would
have to modify the application configuration file of at least four different
application every time that I updated a library file because I can't specify
"use ALL newer files than the one you were compiled with".

Do you know if there is a way to do this in the configuration file without
naming the newer version number directly (i.e. 2.4.*)?

Dave

[Andy]

Dave,

I found somewhere that keeping the AssemblyVersion the same, but
changing the AssemblyFileVer sion would work. Not sure if that would be
useful to you however.

Does using a wildcard in the newVersion attribute work?

Andy

[D. Yates]

> Does using a wildcard in the newVersion attribute work?

I've tried it, but it doesn't work. You can specify a range for the old
version, but you have to specifically target the new version. Like:

<runtime>
<assemblyBindin g xmlns="urn:sche mas-microsoft-com:asm.v1">
<dependentAssem bly>
<assemblyIdenti ty name="mscorcfg"
publicKeyToken= "b03f5f7f11d50a 3a" culture="neutra l"/>
<bindingRedirec t
oldVersion="0.0 .0.0-65535.65535.655 35.65535" newVersion="1.0 .3300.0"/>
</dependentAssemb ly>
</assemblyBinding >
</runtime>

it would be nice if this worked:
<bindingRedirec t oldVersion="1.0 .0.0-1.3.2.65535" newVersion="1.3 .3.*"/>
or

<bindingRedirec t oldVersion="1.0 .0.0-1.3.65535.65535 " newVersion="1.4 .*"/>

Dave

[D. Yates]

> else if ((fvi.FileMinor Part < asname.Version. Minor) ||

(fvi.FileBuildP art < asname.Version. Build) ||
(fvi.FilePrivat ePart < asname.Version. Revision))

Should read:
else if ((fvi.FileMinor Part < asname.Version. Minor) &&
(fvi.FileBuildP art < asname.Version. Build) &&
(fvi.FilePrivat ePart < asname.Version. Revision))

[Andy]

I think you'll have to go the route of only changing the
AssemblyFileVer sion and keeping the value in AssemblyVersion the same.