title: Why do you need to include parent dlls in child asp.net projects?
body: <p>I have a newly created asp.net MVC 2.0 application that is in a completely separate solution from an existing asp.net webforms application.</p>
  
  <p>Because I didn't want the user to have to log in again, I deployed the MVC application in the same site as the existing Webforms app - everything works great.</p>
  
  <p>One thing has me completely perplexed though, the Webforms application uses a Third Party DLL that has nothing to do with my MVC application, yet I can't use the MVC application without including that DLL in the MVC \bin directory.  Why is this required?  It's not part of that application?  It's even causing me issues now so I'm even more curious...</p>
  
  <p>Why is this dependency to the DLL being required in my MVC application? </p>