(Retry) We observed this issue as well. We solved it at the infrastructure level by doing split DNS so that the external name was used internally as well but remapped by the internal DNS serves. This is far from an ideal solution, and one can only hope that the server information moves out of the solution file in future releases...
Mads Orbesen Troest System Architect, M.Sc. Software Development e-mail: [email protected]<mailto:[email protected]> mobile: 6120 6461 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Informi GIS A/S Jægersborg Allé 4, 2920 Charlottenlund, Denmark phone: +45 3996 5900 / fax: +45 3996 5934 / www.informi.dk<http://www.informi.dk/> ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Steven Nagy Sent: 25 January, 2010 06:26 To: [email protected] Subject: SccTeamFoundationServer For some reason this field is stored in the SLN file. This means if different developers connect to it in different ways (some of ours use a local name with our VPN where others use a public facing url) and someone checks in the solution file, we're all in trouble. Think about what kind of impact it would have on workspaces just for starters. Is there a way we can stop this? Can we perhaps move this out of the sln file for future releases? Any techniques for dealing with this? We're using 2010 here. Steven Nagy Readify | Senior Developer M: +61 404 044 513 | E: [email protected]<sip:[email protected]> | B: azure.snagy.name<http://azure.snagy.name/>
_______________________________________________ oztfs mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/oztfs
