c# - Questions on TFS 2017 identity combo-string -


i'm working on upgrading our product' tfs inter-communication code. main idea link work items tfs internal instances in our product , keep content of specific fields synced. earlier target version of tfs 2013 , need upgrade can used 2017. went ok until problem tfs identities popped up. problem in versions earlier 2015 tfs kept identities plain string. combo-string (as mentioned here , here). specific problem i'm receiving identity combo-string in following form:

|john,doe&[some guid]|            // (1) 

and never described in articles, example:

john,doe <john.doe@fabrikam.net>  // (2) 

the guid (referenced [some guid]) appeared internal guid tfs assigned identity. questions following:

  • i can handle identity in code in (1) form of combo-string - format consistent across different tfs installations? - or other hand
  • has encountered same format, because cannot find references on net?
  • should handle identity both ways (1) , (2)?

  • i need test both approaches (apart unit testing) , i'm failing identity combostring in test environment (only production installations affected) - can point me out how achieve this?


Comments

Popular posts from this blog

node.js - Node js - Trying to send POST request, but it is not loading javascript content -

javascript - Replicate keyboard event with html button -

javascript - Web audio api 5.1 surround example not working in firefox -