M
Mark Olbert
I'm in the process of amassing a set of .NET support libraries that I use in many of my projects.
In a number of cases instances of Types from these libraries are created indirectly (e.g., my calling Invoke on a ConstructorInfo
object derived from the Type). Since I strong-name the assemblies this tends to cause a problem as the libraries evolve because the
assembly-qualified name of a Type changes whenever the version of the strong-named assembly changes.
Since this can hardly be a novel issue (but it's not one I've been successful googling, probaby because it's abstract), I'd love to
hear ideas for best practices. Or should I just stop strong-naming the assemblies?
- Mark
In a number of cases instances of Types from these libraries are created indirectly (e.g., my calling Invoke on a ConstructorInfo
object derived from the Type). Since I strong-name the assemblies this tends to cause a problem as the libraries evolve because the
assembly-qualified name of a Type changes whenever the version of the strong-named assembly changes.
Since this can hardly be a novel issue (but it's not one I've been successful googling, probaby because it's abstract), I'd love to
hear ideas for best practices. Or should I just stop strong-naming the assemblies?
- Mark