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

51–60 of 220 posts

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

#51

Post by pnathan »

jf wrote: post #14
ethomson wrote: post #12

Earlier quoted context omitted.

While there are a lot of compelling reasons to use a distributed version control tool, there are also compelling reasons to use a centralized system. Having a lot of giant files (game resources are the canonical example) suits a checkout/edit/checkin system much better than a system that scans the disk like a edit/merge/commit system or a DVCS. These sorts of repositories exist within Microsoft (and DevDiv) itself. F…

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.

> 2: The code your are writing is subject to regulatory control.

Can you expand on what, precisely, you mean by that?

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

#52

Post by cema »

dustinchilson wrote: post #32
gfody wrote: post #31

Git doesn't transplant from the UNIX ecosystem very well. It's why the only options for Git in Windows so far have been as part of a UNIX interop solution like msys, cygwin, interix, etc. It will be really nice to see a proper Git client for Windows especially if it means Windows is also getting a proper SSH.

You can use git from PowerShell and it works almost as well as using bash. Only downside is you have to convert scripts you find online from bash -> powershell

Converting scripts does sound like a serious down side. Are there any automation tools that could help?

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

#53

Post by trevorsg »

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)

Glad you like it! (I work for MSFT and I tested this feature).

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

#54

Post by rwallace »

gfody wrote: post #31

Git doesn't transplant from the UNIX ecosystem very well. It's why the only options for Git in Windows so far have been as part of a UNIX interop solution like msys, cygwin, interix, etc. It will be really nice to see a proper Git client for Windows especially if it means Windows is also getting a proper SSH.

Git on Windows works fine for me, no cygwin in sight. It wouldn't have occurred to me to call msys 'part of a Unix interop solution', though I suppose it does give me a working version of Perl, which is a feature since it was the occasion for me to start using ack instead of grep.

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

#56

Post by xradionut »

jarito wrote: post #15
markstahler wrote: post #13

I am surprised that they are moving towards git and not Mercurial. Isn't Microsoft a sponsor of Mercurial? Perhaps this is because hg already has very good tools for Windows. I suppose I am just a little confused as to why git gets more attention than hg.

The article seems pretty clear on that. "When we made the decision that we were going to take the DVCS plunge, we looked at many options. Should we build something? Buy something? Adopt OSS? We looked at Git, Mercurial and others. It didn’t take long to realize that Git was quickly taking over the DVCS space and, in fact, is virtually synonymous with DVCS."

It's worrying that Git is becoming the OSS "monopoly" in the DVCS space.

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

#57

Post by ben_straub »

gfody wrote: post #31

Git doesn't transplant from the UNIX ecosystem very well. It's why the only options for Git in Windows so far have been as part of a UNIX interop solution like msys, cygwin, interix, etc. It will be really nice to see a proper Git client for Windows especially if it means Windows is also getting a proper SSH.

I've been using git on Windows for years, and while the need for msys stuff is a little clunky, I've never had any problems using it. In fact, the built-in gui tools (git-gui and gitk) work WAY better on Windows than they do on OSX.

libgit2 will eventually make it possible to make a nice GUI client without shelling out to git itself. GitHub for Mac and GitHub for Windows both use it now, and it's way better than parsing shell output.

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

#59

Post by ksherlock »

ajross wrote: post #27
Symmetry wrote: post #23

Apparently libgit2, which they're using for this has the license: libgit2 is under GPL2 with linking exemption. This means you can link to the library with any program, commercial, open source or other. However, you cannot modify libgit2 and distribute it without supplying the source. That sounds nice to me, but I'm not sure how that differs from the standard LGPLv2.

LGPL requires that any distribution be able to replace the LGPL component with a modified version. If you use it as a shared library (er, DLL in this case I guess) you get that for free. But if, for example, you want to link a LGPL library statically you need to provide a static library containing the rest of your program in a linkable form. The point is to allow the user the ability to exercise their right to modify…

That sounds an awful lot like Sun's CDDL.

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

#60

Post by cobrausn »

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)

The amount of code the wizard generates is actually remarkably small - most of the interesting stuff is happening in the base classes. You could probably create a new wizard project and merge in what you need, depending upon the options needed of course.
Post reply on HN