- RT @gblock: Auth0 Extend offsite. Our team is busy cracking away on an MVP @SalesForceDev and @auth0_extend Integration. /cc:@WadeWegner ht… 13 hours ago
- Not sure how a first day could go any better. Met the founders; met my team face to face. @auth0 was the right move. This is going to be fun 1 day ago
- RT @tjanczuk: Just a coffee break during @auth0 offsite #cancun https://t.co/WCK49vHQCw 1 day ago
- The steady flow of awesome ideas for our platform keep coming. twitter.com/auth0_extend/s… 1 day ago
- Just checked into my room in Cancun. Get to meet my whole team at @auth0_extend tomorrow. https://t.co/Sr679VPXNL 2 days 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.