2 ms·

I don't think many people actually dislike the .Net family but it's more the parent company of .Net that causes a lot of dislike to filter down onto ASP.Net and

I don't think many people actually dislike the .Net family but it's more the parent company of .Net that causes a lot of dislike to filter down onto ASP.Net and C#. I have this weird twisted hatred with Microsoft. I think .Net is great but as an iOS dev working inside a Microsoft based team I've founded solutions such as TFS to be just terrible lock ins. I'd probably love Microsoft more if just this once they would of assessed the current source control versions, chosen a popular standard (Git) and then deeply integrated it into VS. What they instead did was give you TFS with a lack of client end Rest API documentation and wrote a terrible cross platform command line tool. You didn't see Apple creating XSourceControl.

StrawberryFrog 16y ago
a Microsoft based team I've founded solutions such as TFS to be just terrible lock ins. The majority of .net development that I have seen is not done on TFS. I've used many source control sustems for .Net code. SVN is far more common. a ".Net dev shop" is far from being the same thing as "a Microsoft only" shop. Typically you see software in use like NUnut, SVN, jQuery, Castle Windsor, TeamCity, Resharper, etc. If you're lucky, you may even get Git or Mercurual. MS could not have standardised on Git even if they'd wanted to - TFS pre-dates Git by a few years. The driver for MS making TFS was two-fold: 1) get people off MS's previous source control system, SourceSafe, which dates back to about 1995. And it shows. SourceSafe is one of the few version control systems that I do not hesitate to say "avoid! Run! Use anything else!" about. TFS is actually a large improvement. 2) To try to prevent them from going to SVN instead, which was the new thing then. Since SVN is lightweight and free, so TFS took the opposite route of being heavyweight, kitchen-sink, ALM, etc.

StrawberryFrog 16y ago

a Microsoft based team I've founded solutions such as TFS to be just terrible lock ins. The majority of .net development that I have seen is not done on TFS. I've used many source control sustems for .Net code. SVN is far more common. a ".Net dev shop" is far from being the same thing as "a Microsoft only" shop. Typically you see software in use like NUnut, SVN, jQuery, Castle Windsor, TeamCity, Resharper, etc. If you're lucky, you may even get Git or Mercurual. MS could not have standardised on Git even if they'd wanted to - TFS pre-dates Git by a few years. The driver for MS making TFS was two-fold: 1) get people off MS's previous source control system, SourceSafe, which dates back to about 1995. And it shows. SourceSafe is one of the few version control systems that I do not hesitate to say "avoid! Run! Use anything else!" about. TFS is actually a large improvement. 2) To try to prevent them from going to SVN instead, which was the new thing then. Since SVN is lightweight and free, so TFS took the opposite route of being heavyweight, kitchen-sink, ALM, etc.