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

71–80 of 220 posts

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

#71

Post by tracker1 »

modeless wrote: post #22
untog wrote: post #17

Earlier quoted context omitted.

I'd argue that isn't really the use case for their free tools. They want you to make ASP.NET web sites, Windows Phone apps and maybe a few simple desktop apps.

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.

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

#72

Post by MichaelGG »

dustinchilson wrote: post #65
pnathan wrote: post #51

Earlier quoted context omitted.

> 2: The code your are writing is subject to regulatory control. Can you expand on what, precisely, you mean by that?

Some code like encryption algorithms cannot leave the United States by law (if developed by a US company/Citizen). Another example might be Credit Card Processing software, you don't want a lot of people knowing how you generate your encryption keys.

If your encryption key generation security depends on people not knowing how you generate keys, then it's totally busted.

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

#73

Post by dustinchilson »

cema wrote: post #52
dustinchilson wrote: post #32

Earlier quoted context omitted.

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?

It's not as bad as it sounds, and you don't have to do it for all scripts.

1) Most scripts will work, you just have to tweak how loops are written and the way you declare functions. 2) If the script uses basic commands like ls, mkdir, etc their are powershell aliases built in already that point to the equivalent PS command.

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

#74

Post by smackfu »

fusiongyro wrote: post #19
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…

The OP is simply saying that it seems odd that Microsoft would pour $20,000+ into Mercurial and then add git support to VS. http://mercurial.selenic.com/sponsors/ I'd bet this is simply a case of the right hand not knowing what the left hand is doing. I had no idea Microsoft were sponsoring Mercurial--even that seems odd, spending money on an open source competitor to a product they also make. I think your analysis i…

It's not like $20k is a lot to Microsoft.

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

#75

Post by darklajid »

ben_straub wrote: post #46
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.

This company here (small.. 40-50 git users) are using GitExtensions, Gitorious - and exclusively ssh for git.

So while I don't claim to be representative, for us that means that this announcement is good news, but not usable so far.

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

#76

Post by steeve »

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…

As a (now former) long time Window developer, and even though people like to bash on it, I still think VS (>2003) is the best god damn IDE I've ever used.

And with .NET it leaves everyone in the dust, IMHO.

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

#79

Post by ryanmolden »

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. :-(

As I have said (here) before, MS is a massive company so anyone making as statement like "MS does X" is almost assuredly wrong.

Devdiv, to my knowledge, as a whole (VS, CLR, etc..) uses TFS. The fork of Perforce the original commentor is talking about is probably Source Depot. When I started at Microsoft we (VS) were still using Source Depot. As I understand it the primary reason was because we had been using it forever (okay, well back to the SLIME days) and there was a massive amount of history in there. Porting it all immediately to another source control provider was a large task. I 'fondly' remember the transition during development of VS 2010. Though to be fair the TFS team was great aboout finding/fixing issues exposed by suddenly onboarding the entire VS team and our possibly 'interesting' source control requirements. I believe Windows still uses Source Depot, likely for similar reasons (the amount of history they have in SD makes the devdiv history seem like a tiny blip).

As for merging problems, I don't know. We routinely merge huge branches with hundreds of thousands of files, including many project files, other XML config files, etc.. and I don't recall many 'insane merging problems' (just your garden variety merging problems that occur with that many files). Then again I am not intimately involved in the merges (other than for occasional fire-drills on files I may have modified). I suppose it also depends on what the changes were on both side of the merge.

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

#80

Post by CurtHagenlocher »

Flow wrote: post #35

This is great news! At work we still use TFS2008 and there doesn't seem to be any way to migrate the source with history except for upgrading the whole TFS installation to a newer TFS. So when TFS2012 is up and running on another machine we are going to move a snapshot. Contrast this to the freedom and "decentrialessness" when using git. MS must seriously use their own products more.

Rest assured, there are tens of thousands of people at Microsoft using TFS -- including nearly everyone in the Server and Tools division which produces Visual Studio and TFS.
Post reply on HN