- Nice I love D3! gag.gl/eK0juj 7 hours ago
- RT @blackgirltech: If you're a Black woman & want to learn how to code but need some financial help, you should apply for the https://t.co/… 18 hours ago
- Louie is growing so fast! https://t.co/hfvOqScGp3 20 hours ago
- RT @vibronet: Open standards should be table stakes for everyone - but won’t be enough to save you from vendor lock-in https://t.co/TbMebtG… 1 day ago
- RT @eugenio_pace: Find out why @auth0’s @vibronet says open standards alone in identity !== vendor lock-in. via @auth0 https://t.co/sRg86Rx… 1 day ago
.NET Assembly References Compile Time Errors
November 5, 2008Posted by on
I have assembly A with class Z that inherits from class X in assembly B. Now in a completely different solution, I have assembly C, which uses class Z.
The compiler complains unless assembly C has a reference to both assembly A & B. Even though assembly C does not use class Z directly in anyway.
Is this expected?
It seems to me that if assembly B is missing at run time stuff blows up, but at compile time it shouldn’t care.
What am I missing here?
My goal is that I can tell my clients to depend on class Z in assembly A, but I can completely reconfigure my assemblies on the other side and have no effect at all on the client when they upgrade.