it's been about a year but it was a death by a thousand papercuts kinda thing.

I want to add that I was not an experienced python developer at the time - I'd used it for a handful of simple automation scripts. My day job was writing scala.

- targeting mono under nginx on linux, from within windows was really difficult, I could never quite get it to work

- no support for monodevelop on windows - cross platform was crucial to me and it just got so onerous. And maybe it's just me, but I was really hitting a lot of frustration with visual studio.

- i wanted to use both yamlschema (broken at the time) and jsonschema (paid)

- msbuild is abysmal with useless error messages. I struggled to run a simple shell script during the build process.

- a couple of libraries I tried were broken or unmaintained. The .net ecosystem seems to have very low quality of community maintained tools.

- no clear guidance around using DAPR without paying microsoft (which i guess is fair, but being vendor locked before I even start is a rough look)

- ... and that's all I can remember. There was more.

I fully acknowledge that some, if not all, of those complaints may be self-inflicted. I can't say that, for my first complicated project in python, it's been completely smooth sailing.

However, with python/falcon, it didn't feel like I was fighting with the ecosystem to define a package, import the package into a microservice codebase, and then get the service running with full test coverage. It didn't feel like I was fighting to bring a third party library in, verify it's actively being maintained, and start using it.

I spent as much time getting a simple microservice hello world with authz/authn validation and a reasonable packaging system, in python, set up in about time as it took me to give up on msbuild.

I've found bootstrapping python microservice development on windows to be quite well supported. I didn't find that with .net.

I think the only time I've found people this far off the main track is users that only know C#/mono coming from Unity Engine.

> targeting mono under nginx on linux...no support for monodevelop on windows

Because you should have never been anywhere near mono.

Even a year ago, if you followed the main .NET documentation it would have directed you to install the .NET 3.1 or 5 SDK on to your linux environment and get setup with VSCode. It's the first step in the hello world tutorial: https://dotnet.microsoft.com/learn/dotnet/hello-world-tutori...

> no clear guidance around using DAPR without paying microsoft (which i guess is fair, but being vendor locked before I even start is a rough look)

Dapr is not a Microsoft product. Microsoft does not offer commercial support for it. There's docs for the .NET library on the Dapr website, along with various community support channels available.

> I've found bootstrapping python microservice development on windows to be quite well supported. I didn't find that with .net.

Bootstrapping a worker service or ASP.NET Core on windows is either a few clicks in VS, or a one line command via the dotnet CLI.

>I think the only time I've found people this far off the main track is users that only know C#/mono coming from Unity Engine.

Damn, almost direct hit. I was a game developer for a year or so about 10 years ago. We were using xna.

Have you tried using .NET Core? It's a pretty thorough reworking of .NET Framework that is officially supported by Microsoft on Mac, Linux, and Windows, and pretty much all of my experiences with it thus far have been positive. VS Code has great built-in support for it.