[masfoobar]

It was not just about C# editing. There were other things being used in Visual Studio at that time. Also being inexperienced in VB.NET (my first job) surrounded by 10 other seasoned devs, they discouraged anything outside of Visual Studio. I understand why when looking back.

This was also the Visual SourceSafe days. How I do not miss that!

C# wiggled its way in eventually.

Back in 2008, I was pretty much using Emacs for most programming languages. The only exception was C# and Javascript.

As the years pass to now, I rarely use a programming language outside of emacs. I have enough years in my career to not tell me what I can and cannot do to get things done.

[finaard]

I had my emacs setup to edit LotusScript (one of the scripting options for Lotus Notes), which is close enough to VB that it could handle the occasional file - this was a new codebase, though, so it made sense to just start with C#.

That was also the project where I tested if git reached the point where you can have "normal" people work with it as well (which worked pretty well). I never accepted any project where they'd have me work with idiotic proprietary source control, unless the project was "migrate away from that".

[masfoobar]

I was happy when I changed job, using SVN (Subversion) instead on Visual Sourcesafe. Then I dabbled a bit with TFS (Team Foundation Server)

Since around 2014 -- It has been Git all the way.

Well, until recently. Codebase at my current job is all contained in a single Subversion repo. It is difficult to maintain and branching takes GBs!

One of my first goals is to move over to Git, and into smaller Git repos. Of course, I have Magit to get it done. :-)