Pipelining MSBuild Custom Tasks

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.


0 Responses to “Pipelining MSBuild Custom Tasks”

  1. Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

TwitterCounter for @anthonyrstevens
Add to Technorati Favorites

RSS Feed

View Anthony Stevens's profile on LinkedIn

%d bloggers like this: