On the CF compatibility is preserved only for dlls where the revision has
changed... In other words when you update a dll make sure that the
major.minor.build numbers are the same as what the EXE was compiled
against...

Note this behaviour is also true for satellite assemblies...

Unfortunately, as far as I know, there is no way to override this
behaviour...

Cheers
Daniel

s/html/Binding_Policy.asp).

assemblies).

Here is a copy of previously posted message to this newsgroup:

------------------------------------------------------------------------
On Compact Framework, there is no configurable policy.

On the Desktop Framework, as you are obviously aware, it is possible to
configure policy for individual applications (or to set system wide
settings) such that applications compiled against one version of an
assembly will run against different versions of the same assembly.  

Do give developers the same benefit on Compact Framework, a certain level
of policy has been "hard coded".

Version numbers are a four part construct in .NET Frameworks, consisting of
Major.Minor.Build.Revision.  On the Compact Framework, assemblies that
differ only in revision are considered compatible.  Therefore, if you're
wanting to replace a single component in your project, you should make
changes only to its revision.

It's important to note that, by default, Visual Studio sets both the Build
and the Revision on assemblies.  To change this behavior, you can edit the
file "AssemblyInfo.cs", which is automatically added to your C# project,
and change the line:
     [assembly: AssemblyVersion("1.0.*")] to
     [assembly: AssemblyVersion("1.0.0.0")]

Jeremy Hance
NET Compact Framework
------------------------------------------------------------------------

Pavel Treskunov
.NET Compact Framework
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------

microsoft.public.dotnet.framework.compactframework:53834

Microsoft claims
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cptutorial
s/html/Binding_Policy.asp).

However, I am experiencing a strange behaviour:
I deploy all my assemblies in a private path.
In my initial deployment assembly A(version 6.0.0.1) references assembly
B(version 6.0.0.1) and everything works fine.
If I deploy assembly B(version 7.0.0.1) without rebuilding assembly A, I
get a TypeLoadException.

This is even stranger:
Assembly A(version 6.0.0.1) also references private assembly C(version
1.0.0.1).
If I deploy assembly C(version 1.1.0.1) without rebuilding assembly A, I
also get a TypeLoadException.

So, does the CLR loader check version numbers or not; How can I override
this behaviour (bindingRedirect will not work because these are private
assemblies).

Thanks in advance