No, not some internal company, just Microsoft being Microsoft. So all Windows pipelines. They also have Linux based pipelines so not completely all pipelines.
But given that a lot of people build dotnet stuff on Azure, the 'windows-latest' image is usually the default. So a lot of pipelines
It’s more the fault of the implementation and documentation.
Yea sure. Though it's slightly XMLs fault for allowing that kinda implementations. Every random thing is in it's own obscure namespace with 20 levels of nested objects in different namespaces, and if you get anything wrong it barely explains what's wrong, and just refuses to work.
It's mostly WCFs fault. I just automatically associate XML with nightmare flashbacks of implementing WCF stuff
In C# I'm using Verify - So I prefer to just use Verify(state); and compare the entire state against a json saved state, instead of manually verifying every individual property
Me: building a fluent interface framework...I already support a WrapperOf<T, T, T, T>User: Can I have a WrapperOf<T, T, T, T, T> because I'm doing something weird?Me: sigh god-damnit. You're right but I still hate it.
Hmm, I'm thinking - We should place a bunch properties and just name them something like "${username}" - "${password}" and variations of that, and see we can "find/replace" cross-site script them into sending their bots details
Yea, I wasn't saying it's always bad in every scenario - but we used to have this kinda deployment in a professional company. It's pretty bad if this is still how you're doing it like this in an enterprise scenarios.
But for a personal project, it's alrightish. But yea, there are easier setups. For example configuring an automated deployed from Github/Gitlab. You can check out other peoples' deployment config, since all that stuff is part of the repos, in the .github folder. So probably all you have to do is find a project that's similar to yours, like "static file upload for an sftp" - and copypaste the script to your own repo.
We also got fully self driving cars in 2 years though, in 2016....