tomcat
tomcat

Reputation: 1860

Teamcity: error MSB3147: Could not find required file 'setup.bin'

C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.target error MSB3147: Could not find required file 'setup.bin' in ... folder

I have seen there are similar messages during the time frame of last upgrade of VS for 2012.

I did not find the registry keys on the build server as mentioned in other posts i.e. Could not find required file 'setup.bin'

I appreciate your help.

Upvotes: 0

Views: 805

Answers (2)

tomcat
tomcat

Reputation: 1860

I don't have SDK installed on the server. I have updated the .csproj with

 <PropertyGroup>
     ...
    <BootstrapperEnabled>false</BootstrapperEnabled>
  </PropertyGroup>

That fixed the build.

Upvotes: 0

Leo Liu
Leo Liu

Reputation: 76670

Teamcity: error MSB3147: Could not find required file 'setup.bin'

According to this blog entry the bootstrapper files are installed during the .NET Framework SDK/Visual Studio IDE install. It also shows the registry entries that are searched to look for the bootstrapper directory.

If one computer that does not have .Net Framework SDK/Visual Studio IDE installed(such as, build server), none of the registry key would be set.

I did not find the registry keys on the build server as mentioned.

You can install .Net Framework SDK/Visual Studio IDE on the build server to get this registry key. If you don not want to install them, you could manually set it up by following steps:

  1. Copy the whole C:\Program Files (x86)\Microsoft Visual Studio 14.0\SDK folder from the local machine with Visual Studio IDE installed to the server.

  2. creating the 14.0 registry key and adding the value:

For 86bits:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\GenericBootstrapper\14.0]
"Path"="C:\Program Files (x86)\Microsoft Visual Studio 14.0\SDK\Bootstrapper"

For 64 bits:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\GenericBootstrapper\14.0]
"Path"="C:\Program Files (x86)\Microsoft Visual Studio 14.0\SDK\Bootstrapper"

enter image description here

Note: Visual Studio must be restarted.

Upvotes: 2

Related Questions