This project is read-only.

Requirements Definition Document

May 6, 2008 at 3:06 PM
I would like to start discussion about requirements on the tool before we begin some work on it. Feel free to write your requirements, suggestions, etc.
May 13, 2009 at 12:22 PM
Edited May 13, 2009 at 12:40 PM

Just a rant here for some requirements where the msdesigner for MSBuild could be an implementation of the the workflow designer. In this type of scenario the tool would give users:

  • The ability to display and update each task as a workflow activity.
  • The ability to include display and work with custom task libraries and show the tasks as workflow activities.
  • The abilty to bind property groups as inputs.
  • The ability to bind external properties (properties passed to the project || msbuild args)
  • The abiltiy to create a mock for the build harness / debug.

I really like the sound of this project. Let me know if I can be of any help: