Wildcarding version in assembly reference

[Kenneth Porter]

Using VS2008. I've got two teams developing different parts of an app, so a
C++/CLI DLL used by a C# app changes frequently. I'm finding that the C#
project team must delete and re-add a reference to the DLL each time its
version changes. Is there some way to wildcard the version number? Ideally
the version should get locked down at build time, not when setting up the
project, and in principle the interface of the assembly shouldn't change
without a minor version number bump. The app should accept any version of
the DLL that matches the major and minor version numbers.

[Hans-Jürgen Philippi]

Hi Kenneth,

are you working with strong-named (signed) assemblies? I'm not that much
into assembly versioning but I guess it should be no problem to tell your
assembly consumer app which versions it should digest.
If you google for "Redirecting Assembly Versions" you'll find an MSDN
article on that topic.

Greetings,
Hans
"Kenneth Porter" <sh*************@sewingwitch.comschrieb im Newsbeitrag
news:Xn*********************************@207.46.24 8.16...

Using VS2008. I've got two teams developing different parts of an app, so
a
C++/CLI DLL used by a C# app changes frequently. I'm finding that the C#
project team must delete and re-add a reference to the DLL each time its
version changes. Is there some way to wildcard the version number? Ideally
the version should get locked down at build time, not when setting up the
project, and in principle the interface of the assembly shouldn't change
without a minor version number bump. The app should accept any version of
the DLL that matches the major and minor version numbers.