- It seems that all technical advice boils down to "Stop, Think, Execute, Verify." Skip any one item on the list and… twitter.com/i/web/status/9… 14 hours ago
- Hey, @shanselman I recently interviewed on @2ndCareerDevs and think it turned out really well. Would love to be a g… twitter.com/i/web/status/9… 15 hours ago
- Hey, @ShawnWildermuth I recently interviewed on @2ndCareerDevs and think it turned out really well. Would love to b… twitter.com/i/web/status/9… 15 hours ago
- Dealing w/Imposter Syndrome: Push through and do what the little voice in the back of your mind says you can't do.… twitter.com/i/web/status/9… 17 hours ago
- Hey, @kyleshevlin my friend @gblock said he has a good story for you. Should he just add himself to the list? github.com/kyleshevlin/se… 18 hours 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.