You can ignore all those TPath imports from the samples. This was just done to get the samples working form both the install directory and from within VS to use the development code.
On your build servers and in most circumstances you should be fine with only installing the 32 bit version and then reference the tasks in your scripts using
- 3.5 --- <Import Project="$(MSBuildExtensionsPath)\ExtensionPack\MSBuild.ExtensionPack.tasks"/>
- 4.0 --- <Import Project="$(MSBuildExtensionsPath)\ExtensionPack\4.0\MSBuild.ExtensionPack.tasks"/>
That will work in 32 and 64 bit build processes.
The 32 and 64 bit assemblies are identical and compiled for anycpu. I think the 64bit installer was created at a time when $(MSBuildExtensionsPath) behaved differently. There may have been another reason, I'll have to think about it, but I'm not convinced we need different flavors now. Some people use the binaries checked into TFS or from a file share and avoid any flavor issues.
Does that help?
Mike