I have recently installed the TFS 2010 RC at my office and am looking to use it for our CI on a new MVC 2 project I have going right now.
Unfortunately, while everything started out great, I ran into a problem because I am using an architectural design known as “onion architecture” – it has other names I’m sure. But the idea is that the .Web project has no references to anything except for the .Core project.During development, I simply configured the Properties dialog of the .DependencyResolution project such that the Output Path is “..\Web\bin\” – this way visual studio copies all the other necessary assemblies for my application into Web during compilation. Since the DependencyResolution has a physical reference to all other projects and assemblies, all of the dlls automatically get copied to the output folder – so I use the Visual Studio Output Path to copy those assemblies in the Web/bin folder
The caveat to this however, occurs when I right click on my Web project and Build Deployment Package. Unfortunately the output of the Deployment Package only includes the DLLs that were physically referenced by .Web. This means the real business logic (meat) of my application is not included with the deployment package.
I am wondering if the following link may point me in the right direction. Perhaps I should create a MyApp.wpp.targets file in the root, but I am unsure what to put in the file to tell MSDeploy to include the files I desire. http://blogs.msdn.com/webdevtools/archive/2010/02/19/how-to-package-com-component.aspx