Samples are available in the codebase, the help file and the online help.


  1. Some samples may work ‘as-is’, whilst others may need some configuration to execute successfully, e.g. entering your computer name, or a specific file path. Most samples are intended to be read and understood, rather than executed.
  1. The samples use a specific import method so that it’s easy for end users to run them from the installation folder and for developers to run them from within the development IDE, e.g.

<TPath Condition="Exists('$(MSBuildProjectDirectory)\..\..\Common\MSBuild.ExtensionPack.tasks')">$(MSBuildProjectDirectory)\..\..\Common\MSBuild.ExtensionPack.tasks</TPath>
<Import Project="$(TPath)"/>

It should not be necessary for you to include the above type of import in your usage of the tasks. If you have used the default installation path, simply use the following imports:
  • 3.5 --- <Import Project="$(MSBuildExtensionsPath)\ExtensionPack\MSBuild.ExtensionPack.tasks"/>
  • 4.0 --- <Import Project="$(MSBuildExtensionsPath)\ExtensionPack\4.0\MSBuild.ExtensionPack.tasks"/>

Last edited Apr 6, 2014 at 9:20 AM by mikeFourie, version 3


Badchenn Oct 29, 2013 at 12:37 AM 
I was able to use the 64 bit version -- $(MSBuildExtensionsPath64) -- in place of the 32bit version. See this link:

medleykupps Sep 16, 2013 at 2:23 PM 
Is there a way to modify the $(MSBuildExtensionsPath) to direct to the MSBuild Extensions folder under 'C:\Program Files' instead of 'C:\Program Files (x86)'?