Home/ Questions/Q 6904829
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-27T08:06:34+00:00

I have a solution with several web application projects in it. After all the

  • 0

I have a solution with several web application projects in it. After all the projects have been built I need to run an MSBUILD script.

What I used to do was call the script from one of the existing projects (through <Target Name="AfterBuild"> in the .csproj file). However, I had to make sure I used the project that built last, and if the build order ever changed I would get unexpected results.

So, I decided to make an empty web application project, and set the project dependencies so that it always built last, then attach the MSBUILD script to this.

So now it always runs at the right time, but I get an extra (tiny) assembly as a result of the supposedly empty project being built. There are no code files in the project (except AssemblyInfo.cs), but an assembly is always produced.

So, is there either a way to stop the assembly being built, or maybe a way to attach the MSBUILD script to the solution as a whole and avoid this dummy project altogether?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In MSBuild 4.0 there are two new hooks that can be used to run scripts before and after a solution is built. When running MSBuild on a solution file, it will look for two target files in the solution directory:

    • before.SolutionName.sln.targets
    • after.SolutionName.sln.targets

    If any of those files is found, it will automatically be executed at the proper stage.

    In your case, in order to run a script after all the projects in the solution have been built, you could create an after.MySolution.sln.targets file with a Target like:

    <Target Name="RunPostBuildScripts" AfterTargets="Build">
    <MSBuild Projects="PostBuild.targets" />
</Target>

    See also:

    • 0