Geeks With Blogs

News
Disclaimer: The views expressed on this blog are my own and do not necessarily reflect the views of my employer.

Creative Commons License


Check out my about.me profile!

INETA Community Speakers Program

Follow enriquelima on Twitter
Locations of visitors to this page

Intentional Thinking Enrique Lima

The problem?

Performing a build on a ClickOnce solution would not be successful due to the setup.bin not being located.

Ok, now what?

Researched from corner to corner, install, re-install, update.  Found some interesting posts to fix the issue, but most of them were focused on Team Foundation Server/Team Build 2008, and some other on 2005.  The other interesting tidbit was the frequent indication to modify the registry to help Team Build find the bootstrapper.

Background info:  This was a migration I posted about a few days ago, a 32 bit TFS implementation to a full 64 bit TFS implementation.  Now, the project has binaries and dependencies on X86 (This piece of information became essential to moving from a failed build to a successful build).

So, what’s the fix?

The trick in this case was to go back into the Build Type and check the properties/configuration.  Upon further investigation, I found the following:  Once you Edit the Build Definition, then select Process, expand 3. Advanced and look for MSBuild Platform, switch from Auto to X86.  Ran the Build, and success!

image

Posted on Tuesday, June 1, 2010 8:23 PM TFS , Visual Studio | Back to top


Comments on this post: A little tidbit on Team Build 2010 and error MSB3147

comments powered by Disqus

Copyright © Enrique Lima | Powered by: GeeksWithBlogs.net