2
Vote

Unable to build the TFS Integration Tool from the code shared

description

We have downloaded the source code from http://tfsintegration.codeplex.com/SourceControl/latest -> "Files" tab (assuming this is the latest code). There were lot of build errors in that solution. Also, there are lot of header files missing. Below is the approximate list of header files missing:
__defs.h,
_mingw.h,
_types.h,
alloca.h,
apr.h,
apr_allocator.h,
apr_errno.h,
apr_file_io.h,
apr_general.h,
apr_getopt.h,
apr_hash.h,
apr_pools.h,
apr_strings.h,
apr_tables.h,
apr_thread_mutex.h,
apr_time.h,
apr_want.h,
Availability.h,
AvailabilityInternal.h,
errno.h,
limits.h,
machine/types.h,
malloc.h,
msclr\marshal.h,
signal.h,
stdafx.h,
stdarg.h,
stddef.h,
stdint.h,
stdlib.h,
string.h,
svn_auth.h,
svn_checksum.h,
svn_client.h,
svn_cmdline.h,
svn_config.h,
svn_delta.h,
svn_diff.h,
svn_error.h,
svn_error_codes.h,
svn_io.h,
svn_opt.h,
svn_pools.h,
svn_ra.h,
svn_string.h,
svn_types.h,
svn_wc.h,
sys/cdefs.h,
sys/limits.h,
sys/socket.h,
sys/wait.h,
wchar.h,
Winbase.h,
Windows.h,
. Please provide these header files.

In response to the blog posted by me: "http://social.msdn.microsoft.com/Forums/vstudio/en-US/ecee405f-06b5-46a5-a9d2-13bc82d0c4ca/unable-to-build-the-tfs-integration-tool-from-the-code-shared?forum=tfsintegration",
it is mentioned that 65711 version should be taken. But it looks like the patches from 65711 version are not applied to the code present in the path (http://tfsintegration.codeplex.com/SourceControl/latest -> "Files" tab). As there are many patches in 65711 version, it would take more time for us to update these patches manually.

Could you please provide us with the complete latest source code including header files and patches (in 65711) applied?

comments

wschaub wrote Sep 16, 2014 at 3:04 PM

Either exclude the experimental SubVersion adapter from your build or see http://subversion.apache.org/docs/api/1.6/index.html for the SubVersion API and associated files.

wrote Sep 16, 2014 at 3:05 PM

FrogPrince wrote Dec 24, 2015 at 2:03 AM

Hi Poornima,

In order to get the code for 65711, browse to here:
https://tfsintegration.codeplex.com/SourceControl/changeset/65711
and then click Download. This will give you a 128 megabyte .zip file with all of the source code for the 65711 release.

That said... you will still have a terrible time building the project. Once you correctly run your \Development\setup_build_environment.bat batch file, which will correctly setup your \Binaries\Internal\TFS2008 and TFS2010 folders, then you will still need to download the source code for Subversion and APR, and put them in the corresponding \ExternalSources\Apr and \ExternalSources\Subversion folders (which you must create), and then you must update the Subversion.Interop project to add the include folder manually for the subversion source you just copied, because it apparently doesn't figure out the include folder correctly...

and after all that... you'll think you're good and ready to compile. But only then will you discover that all of the projects that are targeting TFS11, are somehow magically upgrading their references to TFS12. This is because, like any NORMAL developer (hello, Microsoft, anyone reading there?), you have Visual Studio 2008 installed and Visual Studio 2010 installed AND Visual Studio 2012 installed AND Visual Studio 2013 installed...
and here is the real sucker punch of them all, as the references upgrade to TFS version 12, they cross a boundary where now those assemblies depend on the 4.0 framework (version 11 and prior depended on the 2.0 framework)... so basically, Microsoft has baked in some kind of "automatic" upgrade for the TFS references that has no brains whatsoever, and doesn't even take in to account the fact that project the reference is in isn't targeting the 4.0 framework, nor would it work if it was, because the project, itself, was inheriting from a different 2.0 project.

And of course... the biggest irony of all... is that this project... is THIS project, written and presented by Microsoft engineers in an effort to get people to migrate their private source code stores into Microsoft's cloud (VisualStudio.com). I can't even begin to describe how this is a fail on so many levels.


I'm going to start a separate thread for this issue and while link it here once I do.

wrote Dec 24, 2015 at 2:06 AM