Sometime ago I built a tool I called Build Console. I was a quick and dirty development but until today we are using it often in our daily building.
Why I needed this tool, well I don’t wanna tell you that VS build report is really poor but… it is ;) I don’t wanna open a big solution and wait 5 minutes in order to build my solution.
I known I can use msbuild command line but it is so hard to know what is going on with the build process (how many warining, errors, what project fail, etc).
So that I built a very simple tool that just is listening msbuild and show you the in a better way what is going on with your build.
Additionally it save the history of your builds.
- Open BuildFiles and Solution Files
- Show and Save Build Reports
- Support for cancellation
- Verbosity Configuration
- Build Console solve another small problem that I always have, when building C++ I want a detailed verbosity but for C# projects I need a normal verbosity. BuildConsole assume you want this and if you choose normal when it is building a C++ project it assume detailed. I could be annoying for somebody but I need to know what C++ source is msbuild building and with normal verbosity I can’t see this.
If you are going to use BuildConsole always with the same build file you can use the .config file
<?xml version="1.0" encoding="utf-8" ?>
<add key="BuildFile" value="mybuild.msbuild"/>
If you need the code just drop me a line. Remember it is dirty code ;)
I would like to have a better output in Orcas ;)