Hi,

Assuming you are trying the decompress the .zip file (that is downloaded from here) and you are getting an error message saying that the past is too long, you could try to decompress it in a path with a short length, such as C:\.

If you are talking about the .vsix file, there is not a way to modify the path were it is installed (it should be under the C:\Users\%UserName%\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\Microsoft\Smart Client Software Factory 2010\2.5.0.0) so perhaps a long user name could be the cause of it.

Please let me know if this helps.

Damian Schenkelman
http://blogs.southworks.net/dschenkelman

That path is on a Windows Vista or Windows 7 box, but on an XP machine, the path would be under C:\Documents and Settings\....

... which makes the path longer than the 260 characters.

I was also having problems installing on an XP machine.

From the installer log:

5/16/2011 1:49:04 PM - Beginning to install extension to Microsoft Visual Studio 2010 Ultimate...5/16/2011 1:49:16 PM - Install Error : System.IO.PathTooLongException: C:\Documents and Settings\al08333\Local Settings\Application Data\Microsoft\VisualStudio\10.0\Extensions\Microsoft\Feature Builder Power Tool\1.0\T\P\Extensibility\EPT.zip: ExtenderPackTemplate/templates/projects/feature extensions/featureextension.csproj   at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.BeginInstall(IInstallableExtension installableExtension, Boolean perMachine, AsyncOperation asyncOp)   at Microsoft.VisualStudio.ExtensionManager.ExtensionManagerService.InstallWorker(IInstallableExtension extension, Boolean perMachine, AsyncOperation asyncOp)

I followed the instructions to extract the .vsix file (using WinZip/Rar) to a directory and then edited the extension.vsixmanifest file to change the name 'Feature Builder Power Tool' (as shown in the log lines above) to 'FBPT'. Here's the context:

  <Identifier Id="FeatureBuilder">    <Name>FBPT</Name>    <Author>Microsoft</Author>

These elements are found right near the top of the .vsixmanifest file.

The trick that follows is to create a zip file starting from the directory where the files were extracted to (i.e. NOT including the parent directory that was probably created when you extracted the original .vsix file, something like 'FeatureBuilderPowerTool'). If you open the .zip file you should see something like:

Content (directory)

GeneratedCode (directory)

...

extension.vsixmanifest

etc.

That worked for me ....