"Build VS.Net Solution" action -> "Solution" tab -> "Apply To Project" option

FinalBuilder Bugs
1

Hi,

I am currently using FB6 eval copy and encountering an issue with the "Apply To Project" option under the "Solution" tab for "Build VS.Net Solution" action.

Refer attached FB6_01.JPG, in the solution there are 2 projects "MCS Interface" and "FidelioSPMS". I only wish to build project "MCS Interface" and therefore I left "FidelioSPMS" unchecked. Unfortunately, "FidelioSPMS" still gets built as attached FB6_02.JPG clearly shows.

May I know if this is a problem with FB6 eval copy? Or is there any other setting that I need to configure so that only "MCS Interface" is built without also building "FidelioSPMS" project?

Note that the solution has 2 projects because "FidelioSPMS" is a DLL project used by "MCS Interface". And I do not want to remove "FidelioSPMS" from the solution so that it makes developers' life easier if the solution includes the DLL source code for debugging or code tracing.

Please advise. Thanks.

 

Rgds,

FB6_01.JPG

FB6_02.JPG

2

Hi

My guess is the visual studio/msbuild is automatically building FidelioSPMS because it is not available in the output folder. You should be able to see this in the finalbuilder log for the vs.net action.

3

FinalBuilder 6.1 allows you to override reference paths for the vs.net action, this should enable you to point the action to the folder where the dependant assemblies live, and should stop the other assembly being built.

vsreferencepaths.png

4

Excellent!!! Thanks for the pointer, it is working now as advised running on FB6.1.

Rgds,