[dustinmoris]

Well Visual Studio is certainly not free (maybe the community edition) and therefore I don't think I deserve to be littered with Azure ads all over a tool which costs already a lot of money.

However, my main complaint is not that they advertise their own products, which is absolutely fine, but the way how it is done is starving the .NET community from anything else but Microsoft. The way how all their .NET products are extremely tightly linked to a point where wanting to use something else but Azure or VSTS becomes almost unnaturally difficult, which is what I really dislike. For example, if I look at a nodejs product then I see documentation for all various integration points, with AWS, GC, Azure, etc., but when I look at a Microsoft library there is no documentation or integration points out of the box but Azure and that has a ripple effect on the rest of the community. Every library author only builds their tools optimised for Azure and don't even think about what else there is, which is quite upsetting.

[bonesss]

I don't think this issue is unique to MS, but thanks to their historical business markets (Office, small-to-medium businesses), and product portfolio the sense is that many Azure services are spider-webs of related products. That feeling that you can't just use a component in isolation, but that other tightly bound products are often the only way to serve reasonable services.

They've made substantial efforts and improvements, so credit where credit is due. I think the broader .Net community needs to pull their thumbs out and take a hard look at why C# OSS has struggled the way it has, and how the ecosystem should be maturing.

The cross-platform, OSS-friendly, orientation of the F# community has been much more reflective of my technical concerns, platforms, desires, and predelictions.

[alkonaut]

Github was one of the best integrated services in VS even before ms bought it. But that's beside the point- the point is this: it's on Google and Amazon to make the development story good for their platforms.

So Google and Amazon should be scrambling to perfect the deployment plugins for VS. True, microsoft is SELLING (some editions of) VS - but there I'm sure they weigh both demand from customers AND the potential earnings. If AWS and Azure features are equally in demand, of course they will focus on their Azure features first because they have benfits for Ms.

[scarface74]

Why look at Microsoft documentation then? AWS provides excellent documentation and plug ins for Visual Studio.

[mattmanser]

I use git inside VS, it's fine, I've a few minor quibbles, but all the GUI git tools I've used are a bit shit (tortoisegit, GitHub for Windows).

The built in support for GitHub is fine, so you can stop moaning about VSTS.

Also, you don't have to use azure or SQL server. You can close those tools and, poof, it's done.

One of the more ironic things is that there's a growing dissatisfaction with MS precisely because they're making it more flexible.

Lots of people just want stuff that works with no config, no mucking around with command line tools.

That MS are proudly going 'run dotnet blah' is actually, in a lot of ways, a bad thing. Why can't I just click a button, and why clutter tutorials with lots of pointless command lines?

The 'no hassle, no fucking around with shitty console tools' programming alternative is going away.

[tamrix]

So you want other cloud providers to be a checkbox in the installation rather than a checkbox under extensions and you want to copy the documentation from other cloud providers onto msdn?

That's a pretty easy ask.