0

I have some XSD's files which I generate classes for using the XSD.exe utility from MS.

I use the pre-build to check-out the generated code classes file and the post to check back in.

Since there are several developers working on the same project and this is happening every time each decides to rebuild we keep getting conflicts on it which is not real conflicts (simply caused by a slightly different xsd tool version which is included somewhere in the header of the generated cs file).

To resolve this I wanted to first compare the XSD's content with the source server and only then perform the operation of the check-out + check-in.

Is there a way to do this using TFS?

Note: I tried using the diff command in the tf.exe but it does not return an exit code which i can use to know the result of the compare.

Any help would be much appreciated...

user1037727
  • 1
  • try using the Power Tools' `tfpt uu` command, that will undo any pending change for files that are actually unchanged. If there are any pending changes left, check them in. – jessehouwing Feb 04 '14 at 14:04

2 Answers2

0

You can use tf.exe and execute a get command for the XSD files, and if it returns "All files are up to date" you know that you don't have to do the check out / gen / check in processing

Joon
  • 2,127
  • 1
  • 22
  • 40
0

My advice would be to fix the cause of the problem rather than the symptoms.

When developing, you should try to have your developers and your build server all running with exactly the same set of tools and source code, so you know you'll all get consistent results. You cannot guarantee that the output from two different versions of a tool will always be identical/compatible. Simple mismatching version numbers are no problem, but what if the final program you generate has subtle differences depending on who built it? Fred may never be able to repeat and fix the bug that your customer is complaining of. Or you may think you've patched that major ATL security vulnerability until one day you realise you've been shipping product from a build server you didn't bother to patch.

It's a pretty simple matter to have a standardised install process (a "how to install" document that everyone follows carefully, a box containing the correct set of DVDs, and/or a network folder or source controlled folder containing the set of installers to be used, libraries to be linked to, etc)

Jason Williams
  • 56,972
  • 11
  • 108
  • 137