Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio and Team Foundation Server will have Git support

blogs.msdn.com

Post reply on HN
Print view View original

81–90 of 220 posts

Re: Visual Studio and Team Foundation Server will have Git support

#81

Post by Strilanc »

hahainternet wrote: post #69
Strilanc wrote: post #43

This seems alright, but it definitely feels incomplete. I tried it out with one of my github projects, and the setup wasn't impressive at all. First, it didn't automatically detect that there was a 'GitHub' remote. My first guess was that I needed to call it 'origin', but that didn't fix it. Instead, I needed to go into the command line and specify the master branch's upstream branch like so: "git branch --set-upstre…

Did you actually clone the branch or did you manually set up the remote and branch? I ask because a clone sets the upstream automatically, and inferring the remote from the branch's upstream is the correct behaviour. You can also use the -u flag in push/pull to set this.

In this case I created the project on my machine then pushed it to github at a later time, which is why the upstream wasn't set.

Re: Visual Studio and Team Foundation Server will have Git support

#82

Post by ezquerra »

I'm a TortoiseHg (mercurial GUI front-end) developer and an (occasional) mercurial contributor.

I think this is really great news, both for git, Microsoft and OSS in general. It is definitely a great move for Microsoft.

I hope they also add support for Mercurial in the future. Git is a great tool but I think Mercurial is equally powerful yet easier to use and understand (IMHO). It is not as widely used as git, particularly in OSS circles, but there are many OSS projects (e.g. Python) and many companies (e.g. Mozilla and Facebook) that use Mercurial very successfully. Choosing Git as the first DVCS they support makes a lot of sense, but Mercurial would be a nice second choice.

In particular, being able to use mercurial with TFS would be awesome in an enterprise context. Plus I'm sure all in the TortoiseHg project would welcome the competition if Visual Studio were to get builtin support for Mercurial as well as git :-)

Re: Visual Studio and Team Foundation Server will have Git support

#83

Post by georgefox »

SideburnsOfDoom wrote: post #2

When I read "Q: Does this mean Team Foundation Version Control (TFVC) is dead? A: Not for a second." The thing that comes to mind is a politician saying "I'm not thinking about resigning". His resignation has just become nearly inevitable. I have more belief in the statement about Microsoft working with open source, or at least MS Developer Division working with open source. On the whole this looks cool, though VS in…

Considering Visual SourceSafe's extended support runs through 2017, I think it's safe to say TFVC will be around and supported for quite a while yet.

Re: Visual Studio and Team Foundation Server will have Git support

#85

Post by Strilanc »

ethomson wrote: post #47
Strilanc wrote: post #43

This seems alright, but it definitely feels incomplete. I tried it out with one of my github projects, and the setup wasn't impressive at all. First, it didn't automatically detect that there was a 'GitHub' remote. My first guess was that I needed to call it 'origin', but that didn't fix it. Instead, I needed to go into the command line and specify the master branch's upstream branch like so: "git branch --set-upstre…

It's important to note that this is a "community technology preview", so while we've put a lot of work into this, you're right, it's nowhere near complete. The underlying technology here is libgit2, which currently doesn't support ssh, although it's something that is being worked on. (We'll improve the error message, of course, for the future. We appreciate the feedback.)

I didn't really intend to sound like I was making damning criticism. After setup the process seems fine, and solving those issues only took ten minutes (but ideally they wouldn't occur in the first place).

Re: Visual Studio and Team Foundation Server will have Git support

#86

Post by modeless »

tracker1 wrote: post #71
modeless wrote: post #22

Earlier quoted context omitted.

I'm sure that's their argument too. "Express isn't 'for' that." However, Microsoft is not really in a position now to dictate what developers "should" be using Windows/Visual Studio for. If they want Windows to remain relevant as a platform then putting roadblocks in front of developers is the wrong thing to do, even if the roadblocks are well-intentioned "steering" towards a development path Microsoft prefers.

But most people using the express versions probably aren't building these types of applications.. Also, the download size is important here. You can download the developer libraries GP refers to separately IIRC... Windows SDK etc.

The free Windows SDK doesn't include ATL/MFC either, for several versions now. You have to comb through the Microsoft Download Center archives to find an old download that happens to still have it. (For anyone who's actually looking, you can get it from, of all things, the Windows Driver Kit, version 7.1.0 and below only. http://www.microsoft.com/en-us/download/details.aspx?id=1180... )

Download size is not an issue because Visual Studio Express is primarily installed through a <1MB installer stub these days. You can choose the options you want and it only downloads what you select.

Re: Visual Studio and Team Foundation Server will have Git support

#87

Post by ethomson »

Strilanc wrote: post #85
ethomson wrote: post #47

Earlier quoted context omitted.

It's important to note that this is a "community technology preview", so while we've put a lot of work into this, you're right, it's nowhere near complete. The underlying technology here is libgit2, which currently doesn't support ssh, although it's something that is being worked on. (We'll improve the error message, of course, for the future. We appreciate the feedback.)

I didn't really intend to sound like I was making damning criticism. After setup the process seems fine, and solving those issues only took ten minutes (but ideally they wouldn't occur in the first place).

It wasn't taken as such - and we appreciate the criticism, as we've got a fair ways yet to go. I was just wanting to set expectations appropriately since there's been a lot of excitement around here today and even we have forgotten that this is oh so very rough around the edges.

Re: Visual Studio and Team Foundation Server will have Git support

#88

Post by jcampbell1 »

mitchty wrote: post #45
shanselman wrote: post #25

Earlier quoted context omitted.

One think that I've been impressed with is that changes you make from the command line are reflected instantly in the GUI. I like to change branches from PowerShell with posh-git. I'm using the GUI and command line interchangeably. (Disclaimer: I work for MSFT but not in the git/vs group)

God I wish emacs would do that with magit, though maybe there is some elisp out there that would aide me. Too lazy to look.

File system notifications are proprietary to each OS, so you may not find anything great.

Re: Visual Studio and Team Foundation Server will have Git support

#89

Post by encoderer »

tedunangst wrote: post #84
gianbasagre wrote: post #77

What they should do next: A developer-friendly command prompt/terminal

It's called powershell.

No, not really.

You cannot natively SSH from powershell. You need PuTTY. And Pageant. And... ugh....

A developer friendly terminal is definitely necessary.

Re: Visual Studio and Team Foundation Server will have Git support

#90

Post by stickbranch »

loeg wrote: post #49

Rock on, Microsoft — this is great news for Windows developers. As much as the open source community (of which I am a part) loves to rag on Microsoft, they seem to have recognized the threat of platforms moving off of Windows (Steam, iPads, Android, ...) and are taking reasonable steps to encourage development for Windows (make the developer experience better). This — a reasonable response to a potential threat — is…

But the response is years late, as usual.
Post reply on HN