Hi Richard,
1) I suppose that by "asset" you mean assembly ?
2) Are those "schemes" possibly datasets ?
Each assembly in .NET has a version number that is usually defined in
the AssemblyInfo.cs file by the AssemblyVersion attribute.
Let's say this is your assembly A.
When an other assembly B reference assembly A in B's manifest are
embedded A's name and version (+ public key and culture I think).
Now, if you don't change A's name and version you can change classes in
A, but they must retain their class names, property names, method
signatures, etc. You can change method implementations, add methods, ...
When you install new A assembly in GAC, B assembly won't note any
difference.
So, maybe you don't need to take care of assemblies that are referencing
your assembly.
This is specially true if you build an library that will be used by many
developers.
Regards,
Petar Repac
> Hi,
>
[quoted text clipped - 14 lines]
>
> Richard