http://blogs.msdn.com/msbuild/archive/2005/11/17/493504.aspxThe last two entries walked through how the Compile target is used by the IDE to drive certain features. There are a number of other targets that get called at various times. Several targets exist to help compute project output groups, which are setsen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/msbuild/archive/2005/11/17/493504.aspx#662359Tue, 11 Jul 2006 17:42:31 GMT91d46819-8472-40ad-a661-2c78acb4018c:662359MattI have a question in relation to resolving references and dependency injection. &nbsp;If project A depends on project B and project B depends on assembly C, but the dependency between B and C isn't a compile time dependency, it's a runtime dependency due to dependency injection, how can I have VS and MSBuild include assembly C whenever project A is built? <br> <br>It appears that assembly C is included in the resulting build of project B, but it is not included in the resulting build of project A, probably because the assembly manifest for project B doesn't list assembly C as a necessary resource. <br> <br>Of course, I want to avoid solutions like, including assembly C as a reference in project A and creating an unused declaration in project B to some class in assembly C... <br> <br>Thanks! <br> <br>-- Matthttp://blogs.msdn.com/msbuild/archive/2005/11/17/493504.aspx#8875606Mon, 18 Aug 2008 02:25:45 GMT91d46819-8472-40ad-a661-2c78acb4018c:8875606MSBuild in Visual Studio | DeveloperZen<p>PingBack from <a rel="nofollow" target="_new" href="http://www.developerzen.com/2006/01/07/msbuild-in-visual-studio/">http://www.developerzen.com/2006/01/07/msbuild-in-visual-studio/</a></p>