Strong versioning for framework install?

[davepkz]

Does .NET's strong versioning paradigm mean that if I build an assembly
for the 1.1 framework, a user must have exactly that version (1.1) of
the framework installed? That is, if the user ONLY has .NET 2.0 will
my assembly not work? or will .NET Fx 2.0 be backwards compatible?

thanks
dave

 

[Mattias Sjögren]

Does .NET's strong versioning paradigm mean that if I build an assembly
for the 1.1 framework, a user must have exactly that version (1.1) of
the framework installed? That is, if the user ONLY has .NET 2.0 will
my assembly not work? or will .NET Fx 2.0 be backwards compatible?

It should work with v2.0 too.



Mattias

 

[Mona]

Hello Dave,

A strong named assembly does not pose any problem in
getting called by the framework of different version than
the one it was built with. The only condition here is that
a strong named assembly should reference and should be
referenced by other strong named assemblies only so that
the security of the strongly named assembly is not compromised.

You can refer to the following link for more information:

[Strong-Named Assemblies]
http://msdn.microsoft.com/library/d.../cpguide/html/cpconstrong-namedassemblies.asp

HTH

Mona[Grapecity]