Linus must be grinning :)
Visual Studio and Team Foundation Server will have Git support
121–130 of 220 posts
Re: Visual Studio and Team Foundation Server will have Git support
#122When 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)
This is one feature that Eclipse don't have since you have to refresh everytime there is changes outside the IDE.
Every time someone says VS blows Eclipse I wonder what VS have that Eclipse don't. When I dabbled C# few years ago, I find the textual support for refactoring and such are much lacking in VS IMO. I haven't tried Resharper though.
My brother applaud VS for its WYSIWYG, but you rarely do that when you program in Java.
Re: Visual Studio and Team Foundation Server will have Git support
#123Rock 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.
I agree just because of VsVim alone. :)
http://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3-...
Re: Visual Studio and Team Foundation Server will have Git support
#124Earlier quoted context omitted.
I know nothing about nothing, but having that many projects under the same solution its the biggest clue that you are doing something very wrong. Even if you have a reason to have 40 projects in what should looks like one solution you can still create various solutions files with just the subset of projects you need. No one works on 40 projects at the same time.
Half of those projects could be class libraries. You can't put those in different solutions cause you miss the whole point of having everything tied up.
We don't have hundreds of millions LoC, but we have a couple of million. We solve the problem you are describing with svn:externals, pulling in the DLL/PDB from other project/solutions as needed on svn up.
I agree it's not as comfy as having everything in one big solution, but being able to count your compile time in seconds as opposed to minutes makes it worthwhile.
Re: Visual Studio and Team Foundation Server will have Git support
#125Earlier quoted context omitted.
Yes, agreed (having worked on middlish-big projects with maybe 40 VS projects for each solution, 45+ minute re-compile times (not from scratch) on the latest gen CPUs, etc) with several hundred million LoC but believe me, if you think that's bad, you don't want to see Eclipse/NetBeans/XCode/etc. with a project a thousandth of that size.
I know nothing about nothing, but having that many projects under the same solution its the biggest clue that you are doing something very wrong. Even if you have a reason to have 40 projects in what should looks like one solution you can still create various solutions files with just the subset of projects you need. No one works on 40 projects at the same time.
It's sadly far too common for .NET developers to carve up their solutions into far more projects than are necessary. This can seriously slow down compilation times.
Re: Visual Studio and Team Foundation Server will have Git support
#126Re: Visual Studio and Team Foundation Server will have Git support
#127Earlier quoted context omitted.
I'm curious, what Java IDE is 10K miles ahead of Visual Studio 2012/C# in your experience? Have you recently used VS with C#?
Haven't used 2012, but I think that IntelliJ IDEA is much better than VS 2010, anyway. Not to knock on 2010, but IDEA is pretty amazing.
Sorry but I don't share your view. I am using IDEA everyday (Python). It's great, but it's a HUGE memory and CPU hog (although IDEA 12 is much better). I always lament VS...
Re: Visual Studio and Team Foundation Server will have Git support
#128Earlier quoted context omitted.
You've obviously never suffered a large project. Crashes, memory gobbling, random debugger failures, glacial speed, lag, project configuration corruption, UI glitches, refusing to load projects, half complete refactoring operations, search/replace just stops, having to reset environment at least once a day, grey screen of death. And that's just the IDE. CLR is the only framework and language combo I've used which wil…
Yes, agreed (having worked on middlish-big projects with maybe 40 VS projects for each solution, 45+ minute re-compile times (not from scratch) on the latest gen CPUs, etc) with several hundred million LoC but believe me, if you think that's bad, you don't want to see Eclipse/NetBeans/XCode/etc. with a project a thousandth of that size.
If a single project is several hundred million lines of code, VS probably isn't the problem.
Re: Visual Studio and Team Foundation Server will have Git support
#129Earlier quoted context omitted.
Yes, agreed (having worked on middlish-big projects with maybe 40 VS projects for each solution, 45+ minute re-compile times (not from scratch) on the latest gen CPUs, etc) with several hundred million LoC but believe me, if you think that's bad, you don't want to see Eclipse/NetBeans/XCode/etc. with a project a thousandth of that size.
I know nothing about nothing, but having that many projects under the same solution its the biggest clue that you are doing something very wrong. Even if you have a reason to have 40 projects in what should looks like one solution you can still create various solutions files with just the subset of projects you need. No one works on 40 projects at the same time.
We have a solution with more than 80 C# projects, and visual studio 2010/2012 handles it fine on modest hardware. I usually hit shift+F6 to build just the current project when I'm iterating on some change. This builds very fast because our individual libraries are small. It doesn't really feel "wrong".
Re: Visual Studio and Team Foundation Server will have Git support
#130Anyone know if there is a way to convert a TFService repository from TFVC to git? I'd like to convert a new project, not yet started that id full of the backlog and test cases, etc...