# Build VS.Net Solution FB4 vss FB5

**URL:** <https://www.finalbuilder.com/forums/t/build-vs-net-solution-fb4-vss-fb5/2930>\
**Category:** Bugs\
**Created:** [November 22, 2007, 10:38am UTC](https://www.finalbuilder.com/forums/t/build-vs-net-solution-fb4-vss-fb5/2930 "2007-11-22T10:38:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![deleted\_user](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/deleted_user/32/937_2.png) [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)\
**Post date:** [November 22, 2007, 10:38am UTC](https://www.finalbuilder.com/forums/t/build-vs-net-solution-fb4-vss-fb5/2930/1 "2007-11-22T10:38:27Z")

</div>

Hi,

&nbsp;

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"&nbsp; /t:Build /p:Configuration="Release";Platform="Any CPU";OutputPath="bin\Release"

&nbsp;

in FB5 however with the same parameters we only get the myfile.dll as output, no real deployment has been done.

msbuild: msbuild "c:\myfile.sln"&nbsp; /t:Build /p:Configuration="Release";Platform="Any CPU"

notice that ;OutputPath="bin\Release" is no longer there.

&nbsp;

&nbsp;

Your comment please.

---

<div class="post-metadata">

**Author:** ![angus](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/a/b3f665/32.png) [@angus](https://www.finalbuilder.com/forums/u/angus)\
**Post date:** [November 22, 2007, 11:23am UTC](https://www.finalbuilder.com/forums/t/build-vs-net-solution-fb4-vss-fb5/2930/2 "2007-11-22T11:23:40Z")

</div>

Hi Christophe,   
  
 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.   
  
 Vincent gives a better explanation in this thread: [https://www.finalbuilder.com/Default.aspx?tabid=53&forumid=6&tpage=1&view=topic&postid=2849#2851](https://www.finalbuilder.com/Default.aspx?tabid=53&forumid=6&tpage=1&view=topic&postid=2849#2851)   
  
 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.   
  
 Regards,   
  
 Angus

---

<div class="post-metadata">

**Author:** ![angus](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/a/b3f665/32.png) [@angus](https://www.finalbuilder.com/forums/u/angus)\
**Post date:** [November 22, 2007, 11:25am UTC](https://www.finalbuilder.com/forums/t/build-vs-net-solution-fb4-vss-fb5/2930/3 "2007-11-22T11:25:08Z")

</div>

Christophe,

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.

Regards,

&nbsp;

Angus