3 ms·
The absolute worst part is all the legacy bits that Microsoft made and later abandoned. We set up a Microsoft Service Center Orchestration service for Windows 2
by moksly 7y ago
The absolute worst part is all the legacy bits that Microsoft made and later abandoned. We set up a Microsoft Service Center Orchestration service for Windows 2012, and while we’re migrating it to Azure now, the C# library that handled authentication became obsolete in 2014, at least to Microsoft. Which means that even with 100% Microsoft tech, you still have to build your own library extensions if Microsoft moves another direction.
It’s like that with a lot of our systems, and it’s pushed us more and more from C# to Python where a lot of things are just easier.
- goto11 7y agoThat seems unrelated to the language of the library though.
- moksly 7y agoThe library was a part of .NET version 4.x and was then dropped when Microsoft wanted people to move to Azure. We had similar issues with the AD APIs in .NET. You’d think Microsoft would have extensive AD integration support for C#, but you’d be wrong. It’s nothing you can’t fix by overriding the standard libraries with extensions of your own, but it’s a lot of work. Which is kind of the opposite of why you’d pick C#. At least in my opinion, you pick it because it comes with a powerful IDE and powerful standard libraries, but it turns out that it doesn’t actually do that once you dig a little deeper than standard CRUD applications.
- goto11 7y agoI feel you pain. But how would it have been any different if the library had been in Python?