I'm using VS2008 (just in case it matters), and I have a solution with multiple projects, some are class libraries, and some are build tools, which the main web project is dependent on. Until now I have been publishing with VS right click publish project, and everything builds and deploys correctly.
I've tried creating a few simple publish scripts using MSBuild and msdeploy.
When I add the "WebProjectOutputDir" property, things get messy:
The build bin tree gets built correctly more or less (at $outdir), however at WebProjectOutputDir, the \bin* subdirectories (which I have resources in) aren't being created at all, and all the files are dumped in \bin !
Some basic research have led me to this, http://geekswithblogs.net/JenniferZouak/archive/2009/11/17/team-build-msbuild--missing-loosely-coupled-and-satellite-assemblies.aspx // http://forums.asp.net/p/1043621/1534682.aspx, which seems to exist from VS2005, and if I'm correct hasn't been solved in VS2010! I do not want to 'hack' my way into solving this by changing the MS build targets files manually.
What would be the correct way to build my project and get it ready for msdeploy to publish, without manually specifying which files to copy, in such a way that the correct build tree structure will remain intact (all my class library resources), just like the right click publish works.