Oct 5, 2010 at 9:55 AM
Edited Oct 5, 2010 at 10:45 AM
Actually, you can but the ExtensionPack in your source tree. The way to do it is to add the ExtensionPack dll's in a "known" directory structure. The way I made it work was to put the dll's in "\Tools\MSBuild Extension Pack\ExtensionPack\4.0".
Then I referred to the extensions path property to the tools directory, like this;
<MSBuildExtensionsPath>$(ToolsDir)\MSBuild Extension Pack</MSBuildExtensionsPath>
Where 'ToolsDir' is the path to the tools directory in our source tree. And i put the .tasks-file there as well;
Importing the extension pack;
Seems like there's a presumption somewhere that the ExtensionPack dll's need to be under the specific directory structure '\ExtensionPack\4.0'.