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

41–50 of 220 posts

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

#41

Post by aardvark179 »

Moto7451 wrote: post #21
tobyjsullivan wrote: post #16

Earlier quoted context omitted.

I think you first have to ask why Microsoft is supporting git when Team Foundation is, itself, Microsoft's primary source control system. The answer is most likely because people use git. Lots of people use git - particularly the crowd Microsoft is actively struggling to appeal to which is the entrepreneurial/startup crowd. I've never used hg so I can't attest as to which is "better" but I really don't think that mat…

I've been an hg fan for a while and like it better (hg jives with my brain better and git occasionally throws weird problems at me) but quality wise I can't say there is much of a difference in my experience. That said, I have never met a single other person who uses hg. Not at work or hackathons. Most have never even seen an hg repository and some haven't even heard of it. Git definitely has "won" this "war".

We use hg for all our stuff at work, and all the openjdk stuff uses it too.

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

#42

Post by ethomson »

Flow wrote: post #39
forrestthewoods wrote: post #36

Earlier quoted context omitted.

MS uses a custom internal-only fork of Perforce. They've used it for quite some time now. It was considered a "competitive advantage" so they used that while Visual Source Safe (lol) and TFS were used by the outside world.

I know, and it shows. This is exactly what the VS/TFS/Azure team must stop doing. Edit: I can't reply to your comment for some reason. If they do use their own tools, how come it's so easy to get insane merging problems on so many of the xml files in use by a VS project? Especially the .dbml files, but also the project files. :-(

Both the Visual Studio and TFS teams use, obviously, TFS for version control. Parts of the TFS team are using git and some of the team is using git-tf, but mostly it's straight up TFVC. But the VS and TFS teams do not use source depot (the aforementioned internal-only perforce-like tool.)

Edit: as for merging XML files -- TFVC uses a standard automerge algorithm, very similar to the one git uses. I'm not sure why you're having merge problems with your XML files, but I'm also not sure it's TFS's fault. But it would be interesting if you filed a connect bug for us to take a look at!

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

#43

Post by Strilanc »

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-upstream master GitHub/master".

Second, as soon as I tried to fetch I got "An error was raised by libgit2. Category = Net (Error). This transport isn't implemented. Sorry". Turns out I have to use the 'http' link instead of the 'ssh' link as the remote destination.

Both of these errors could have been avoided automatically, or at least given better help. Branch has no upstream? Assuming that it's the only remote branch with the same name is a pretty good heuristic, especially when you do no work without user action. Don't support SSH? Try the obvious HTTP alternative, or tell/ask the user to try it.

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

#44

Post by modeless »

Flow wrote: post #37
cobrausn wrote: post #8

Earlier quoted context omitted.

If you wish to make a Visual Studio style application, there are few quicker options than MFC. You get a lot of functionality just with the wizard generated app.

This is a tad off-topic question, but what do you do if you use that wizard and then work on the app for a bit, and then realize you forgot to cross one of the options in the wizard? (I've not used VC++ since version 5 or 6)

There's no way to change your wizard selections after project generation. You have to dig into the project settings dialogs and change the options manually. Or you could generate a new project with the right settings and merge your code into the new project. I'd say it's worth learning how to manually change the project settings, though, if you're going to be working with Visual Studio for any length of time.

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

#45

Post by mitchty »

shanselman wrote: post #25
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…

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.

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

#46

Post by ben_straub »

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…

Libgit2 contributor here. The SSH transport is actually in progress, so this specific issue will go away fairly soon. I'll agree that the error message could be better, but my gut feeling is that most people will clone from within VS and use the HTTPS transport anyway.

This is very much a pre-version-1.0 UI, but I like the direction they're taking it. Really in touch with what their users want and need.

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

#47

Post by ethomson »

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.)

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

#48

Post by to3m »

rjzzleep wrote: post #34
jf wrote: post #14

Earlier quoted context omitted.

A couple of other reasons to use centralized version control: 1: You are a Fortune 100 company and need to have access control on your codebase (so you can give contractors access to only a few files for example) 2: The code you are writing is subject to regulatory control.

sorry, help me understand here. How does something who's only method of control is tied to the ide you use keeping any control over the source code? you can still use git-tfs to use tfs like you would use svn. you can also just copy the file to another folder and suddenly everything is good. or you use time machine or another other backup mechanism. Do i miss something magic that tfs does, that I don't understand?

I can't speak for TFS, so maybe they do something daft, but it's usual that when you get latest from the server you simply won't get the files you aren't allowed to. You won't even see them. It's access control at a finer grain than the repository level, applied on the server side.

(with git always giving you the whole repository, there's not much you could do with git, but but many systems don't do that.)

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

#49

Post by loeg »

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 a huge step for Microsoft. Kudos, VS team.

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

#50

Post by cema »

Moto7451 wrote: post #21
tobyjsullivan wrote: post #16

Earlier quoted context omitted.

I think you first have to ask why Microsoft is supporting git when Team Foundation is, itself, Microsoft's primary source control system. The answer is most likely because people use git. Lots of people use git - particularly the crowd Microsoft is actively struggling to appeal to which is the entrepreneurial/startup crowd. I've never used hg so I can't attest as to which is "better" but I really don't think that mat…

I've been an hg fan for a while and like it better (hg jives with my brain better and git occasionally throws weird problems at me) but quality wise I can't say there is much of a difference in my experience. That said, I have never met a single other person who uses hg. Not at work or hackathons. Most have never even seen an hg repository and some haven't even heard of it. Git definitely has "won" this "war".

I use hg for personal projects, but I agree that git has become almost a standard, and, as others mentioned, almost synonymous with the distributed version control systems. My feeling is the differences between git and hg are smaller than the advantages of switching from one to the other and reconditioning yourself to a slightly different work mode. (I guess I should have said "reconditioning myself".)
Post reply on HN