What scenarios are possible where the VS C# compiler would not compile a reference of a reference?

Posted by SuperKing on Stack Overflow See other posts from Stack Overflow or by SuperKing
Published on 2009-03-11T23:44:21Z Indexed on 2010/04/19 2:03 UTC
Read the original article Hit count: 288

Hello,

I'm probably asking this question wrong (and that may be why Google isn't helping), but here goes:

In Visual Studio I am compiling a C# project (let's call it Project A, the startup project) which has a reference to Project B. Project B has a reference to a Project C, so when A gets built, the dlls for B gets placed in the bin directory of A, as does the dll for C (because B requires C, and A requires B). However, I have apparently made some change recently so that the dll for Project C does not go into the bin directory of Project A when rebuilding the solution. I have no idea what I've done to make this happen.

I have not modified the setup of the solution itself, and I have only added additional references to the project files. Code wise, I have commented out most of the actual code in Project B that references classes in Project C, but did not remove the reference from the project itself (I don't think this matters). I was told that perhaps the C# compiler was optimizing somehow so that it was not building Project C, but really I'm out of ideas. I would think someone has run into something similar before

Any thoughts? Thanks!

© Stack Overflow or respective owner

Related posts about c#

Related posts about visual-studio