Using version independent references

Is there a way to reference an assembly and not be bound to a specific version of that assembly? If the version of our product is 1.0.300.1 and I build applications that reference this assembly, it appears that I am locked into a version of 1.0.300.x. I understand I can increment the last digit without affecting references, but what if I want to upgrade my application to version 2? (IE 2.0.0.0). It appears I break compatibility even though my interface may not have changed.

Thanks for any help on this,

Rich

[517 byte] By [rjhdakota] at [2007-12-16]
# 1

Well according to this all you have to do is not use strong names...

<quote>All versioning of assemblies that use the common language runtime is done at the assembly level. The specific version of an assembly and the versions of dependent assemblies are recorded in the assembly's manifest. The default version policy for the runtime is that applications run only with the versions they were built and tested with, unless overridden by explicit version policy in configuration files (the application configuration file, the publisher policy file, and the computer's administrator configuration file).

Note Versioning is done only on assemblies with strong names.</quote>
DMan1 at 2007-9-9 > top of Msdn Tech,.NET Development,.NET Base Class Library...
# 2
You can use a publisher policy to allow a later version of an assembly to load.
Raptorman515 at 2007-9-9 > top of Msdn Tech,.NET Development,.NET Base Class Library...

.NET Development

Site Classified