Hi,
1. The .Net Project Compiler Action has no Output path property. This means the output path of the project file is used, which is useless in an automated build scenario, since most if not all build will have subsequent actions that need the path of the newly build assembly and there is no way of getting that information.
So please add an Output property that will override the output path given by the proj file, so that consistent builds can be made.
2. The .Net Solution Compiler Action misses alot.
First of all it seems weird to me that unlike NAnt this action was implemented using Visual Studio. Now you already have a project compiler that is uncoupled from VS, please make the Solution task, simply parsing the project references and sorting the build order is all thats needed.
Second we need a Assembly References property and an Output property here as well.
I hope you agree with my findings and will be able to include this in a soon-to-be release.
Best Regards,
Thomas Scheelhardt
Posted By Thomas Scheelhardt on 27 Apr 2006 4:21 AM
Hi,
1. The .Net Project Compiler Action has no Output path property. This means the output path of the project file is used, which is useless in an automated build scenario, since most if not all build will have subsequent actions that need the path of the newly build assembly and there is no way of getting that information.
So please add an Output property that will override the output path given by the proj file, so that consistent builds can be made.
You can control the output paths by creating a configuration in Visual Studio which puts the files where you want them and then.Hi,
1. The .Net Project Compiler Action has no Output path property. This means the output path of the project file is used, which is useless in an automated build scenario, since most if not all build will have subsequent actions that need the path of the newly build assembly and there is no way of getting that information.
So please add an Output property that will override the output path given by the proj file, so that consistent builds can be made.
2. The .Net Solution Compiler Action misses alot.
First of all it seems weird to me that unlike NAnt this action was implemented using Visual Studio. Now you already have a project compiler that is uncoupled from VS, please make the Solution task, simply parsing the project references and sorting the build order is all thats needed.
Second we need a Assembly References property and an Output property here as well.
I hope you agree with my findings and will be able to include this in a soon-to-be release.
Best Regards,
Thomas Scheelhardt
We chose not to go down the Nant path once microsoft announced that MSBuild would be the underlying build engine for vs.net 2005. For VS 2005 projects, you can also use the MSBuild Action in FinalBuilder and set properties such as OutputPath etc. We are looking at doing some more actions which leverage MSBuild to make it easier to work with VS.NET Solution projects.