We have recently switched from finalbuilder v4.1.0.267 to v5.5.0.348
After converting the projects we had problems with the Build VS.Net solution.
In FB4, we could deploy "webstie .solution" into the _PublishedWebsites substructure with the full website in it (images, ascx pages, config files ...)
settings:
solution file c:\myfile.sln
configuration Release|Any Cpu
VS.Net version: VS.Net 2005
use msbuild: yes
all projects in solution : yes
the log file shows this msbuild path: msbuild "c:\myfile.sln" /t:Build /p:Configuration="Release";Platform="Any CPU";OutputPath="bin\Release"
in FB5 however with the same parameters we only get the myfile.dll as output, no real deployment has been done.
Specifying the output path was actually a workaround for prerelease versions of VS 2005 (it would not load the OutputPath from the solution file, so we hard-coded it to bin<config>.)
Modern versions of MSBuild (post-RTM 2.0) should load this setting just fine from the solution file, so it should use whatever is set for that configuration in the solution.
If you need to override the OutputPath, I suggest using the “MSBuild Project” action to build the solution. You can specify “OutputPath” on the Properties page.
I just read your post again, and I cannot explain why the change is preventing the web site from copying properly. If you try the workaround I describe with the MSBuild action, does it give you the desired behaviour?
It's possible that the bug we worked around remains a problem for some project types.