Software development industry analysis by Larry O'Brien, the former editor of Software Development and Computer Language
Thursday, December 08, 2005

It can be hard, when using MSBuild, to know what Tasks (aka Targets aka functions) are available, especially when using the built-in .targets files associated with the compilers. So, I wrote a custom Task that iterates over all the other Tasks that are currently loaded and outputs their [Output] properties. To use it, just drop the .DLL so that MSBuild can find it, open your existing MSBuild project file, and add the following:

<UsingTask AssemblyFile="TasksAndOutputs.dll" TaskName="TasksAndOutputs"/>
<Target Name="AfterBuild">
   <TasksAndOutputs/>
</Target>

And run MSBuild.

Binary and Source-Code Download.

Oh, it's also a decent-enough sample of extending MSBuild with a custom task.

Thursday, December 08, 2005 2:17:38 PM (Hawaiian Standard Time, UTC-10:00) |  Disqus link  | Knowing#
Search
About Larry...
Flickr photostream
Subscribe: RSS 2.0 Atom 1.0
Popular Articles
Programming Sabre with Java, C#, and XML
Genetic Programming in C#
15 Exercises To Know A Programming Language
Top 10 Things I've Learned About Computers From the Movies and Any Episode of "24"
Recently Published Articles
HI
KonaKoder
Categories
Archive
Admin Login
Sign In
Toolroll