Tfs build plugin

Based also on the work done by @pombeirP for TeamCity...

At the moment, it works for me...

States are shared with #2166...

Contrary to TeamCity and Jenkins, there is no web api shared by a TFS server :(

That's why I have created 2 projects that use the tfs assemblies for the 2 version of Visual Studio that support a TFS(Git) repository...

PS : Perhaps, you won't be able to build these project because the tfs assemblies are needed (installed with Visual Studio or [Team Explorer for Microsoft Visual Studio](http://www.microsoft.com/en-us/download/details.aspx?id=40776) ) I wonder if I should better build these assemblies and add the dlls in references. What do you think about that?

Just glancing at the code: why is port 8080 hard coded? Does TFS *always*
listen to 8080? Or can TFS also be configured to another port? (If so then
the port number should also be configurable in GitExtensions).
On Aug 15, 2014 9:12 AM, "Janusz Białobrzewski" <notifications@github.com>
wrote:

> In Plugins/BuildServerIntegration/TfsInterop/TfsHelper.cs:
>
> > +
> > +            try
> > +            {
> > +                string url;
> > +                if (_isWebServer)
> > +                {
> > +                    _hostname = _hostname.TrimEnd('\\', '/');
> > +                    url = _hostname + "/" + teamCollection;
> > +                }
> > +                else
> > +                {
> > +                    url = "http://" + _hostname + ":8080/tfs/" + teamCollection;
> > +                }
> > +
> > +                // Get a connection to the desired Team Foundation Server
> > +                var tfServer = TeamFoundationServerFactory.GetServer(url, new UICredentialsProvider());
>
> Great! BTW: I noticed that TeamCity doesn't build release/* branches - can
> it be configured to do so?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/gitextensions/gitextensions/pull/2167/files#r16282325>
> .
>