Pipelining MSBuild Custom Tasks

Software

I’m working on a thorny little problem right now that I’m having a little difficulty getting my mind wrapped around. I’m developing a custom MSBuild task (the first of several) that has a dependency on Library A; the build task is then used to help build Library B. The goal here is to allow concurrent development on both A and B and not have any build breaks.

Can I do this in one fell swoop?

Build A
Build Custom Build Task and Deploy to the MSBuildExtensionsPath
Build B

In theory it sounds good, but….the devil is in the details.

Share and Enjoy:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • Furl
  • Ma.gnolia
  • Reddit
  • TwitThis
No Comments

Leave a Reply

Allowed tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">