General
MSBuild Sidekick is a visual editor providing rich Graphic User Interface for editing
MSBuild project files. The build project files may be either created as Microsoft
Visual Studio© 2005 build projects, Team Foundation Team Build build
types or custom build scripts.
Version 2 of MSBuild Sidekick is available.
View screenshot
MSBuild Sidekick provides the following features (since version 1.0):
- Load and modify any file complying to MSBuild schema
- View build project structure in a tree view that displays tasks used in build, property
groups and properties, item groups and items, targets and targets tasks and imported
build projects.
- Show or hide presentation of imported definitions in a project tree view
- View MSBuild project raw XML source as you modify the project
- Modify project default targets
- Add or remove tasks used in build project from external assembly
- Add, remove or modify property groups
- Add, remove or modify properties in property groups
- Add, remove or modify item groups
- Add, remove or modify items in item groups
- Add, remove or modify targets
- Add, remove or modify selected target's tasks, tasks order
- Modify selected task properties (including output properties specification)
- Import or remove external build projects
- Open any imported project from the loaded project
Version 1.1 of Build Sidekick provides the following bug-fixes and features
(in addition to features available in version 1.0):
- Inputs and Outputs attributes of target elements are supported in UI
- Load and allow modification of invalid (with missing imports) MSBuild projects
- Elements unsupported in UI are not affected during modification
- BUG FIX: when loading, updating and saving existing MSBuild project, the elements
order in file is not changed
- BUG FIX: when loading invalid MSBuild project, extended error information is supplied
- BUG FIX: comments removed according to elements modified/removed
Version 1.1.2 of Build Sidekick provides the following bug-fixes
- BUG FIX: when loading project with import elements with conditions, the imports
were not loaded if condition evaluated to false
- BUG FIX: when assembly with identically named MSBuild tasks is loaded (even when
tasks are in different namespaces), it is impossible to select tasks for using task element.
Most importantly, SDC tasks assemblies were affected by that bug
- BUG FIX: when loading certaing invalid projects, application failed instead of exiting
gracefully with an error message
Please note, that upgrade from version 1.1 to version 1.1.2 is recommended only if you were affected by some of
the bugs fixed in version 1.1.2.
See Sidekicks blog for more details and usage
patterns.
See also Team Foundation Sidekicks and
Team Foundation Sidekick add-in applications.
Download
Download version 1.1.2 of Microsoft
Build Engine Build Sidekick
Legal
The application version 1.1.2 is a freeware and may be used for any commercial or
noncommercial purpose under the
license.
Intended usage
MSBuild Sidekick application's objective is to assist MSBuild users in creating
and supporting large and complicated MSBuild project files. The project elements
are displayed in tree view hierarchy structure so viewing of even complicated projects
structure becomes easy.
The application provides concise and efficient GUI for the purpose of creating,
modifying or removing any element supported by MSBuild schema, so in-depth knowledge
of XSD schema details becomes unnecessary.
The Sidekick user may easily add any build task defined in external assembly. The
assembly task may be added by using assembly file path or assembly name; the user
may choose to use all or specific build tasks available in the assembly. MSBuild
defaut tasks are available without any special configuration.
The imported project files are open with single click and are avilable for view
or modification in the new instance of MSBuild sidekick. Alternatively, the user
may view all imported elements in same project view.
Implementation notes
The application uses custom XML-based object model for the purpose of editing
MSBuild project files. The compliance to MSBuild schema and imports handling is
assured using MSBuild object model classes.
Feedback
We would be very thankful for any
feedback on application usage, desirable features and found bugs.
Acknowledgements
We would like to thank for participation (order does not imply anything):
- Justin Angel
- Sayed Hashimi
- Steve St. Jean
- Jesper Hogstrom
- Doron Neumann
- Nathan Jones
- John Moshakis
- Vipin Goal
|