3 ms·
Microsoft have best most fascinating documentation in some cases. It can be fantastically detailed, while being completely useless at the same time. Take their
by mrweasel 7y ago
Microsoft have best most fascinating documentation in some cases. It can be fantastically detailed, while being completely useless at the same time.
Take their Azure Python API, which is clearly translated directly from C#: There's a number of functions, which according to the documentation takes a string as an input. The thing is that it won't actually take a string, it will take three or four predefined strings. Everything else will yield no result. The only thing Microsoft doesn't care to put in the documentation is which strings are actually valid and what result you can expect from them.
- heyoni 7y agoThis is slightly unrelated but there was a time when reading the azure docs where you’d be reading a page for version 1.0 but the sidebar would take you to the documentation for version 2.0 and I actually got caught up writing a mismatched integration and it took me forever to figure out why I had done that.
- fernandotakai 7y agomicrosoft's documentation for anything other than .NET stuff is absurdly bad. i was trying to do some work with their crm solution it took me a literal week to find out how to do simple oauth -- mostly because 99% of the documentation only had .NET examples using their own framework!
- Nullabillity 7y agoMicrosoft's documentation for .NET is also absurdly bad. No, I don't want to do a full reload for every overload of a method. Yes, I might want to see where these extension methods are popping up from, out of nowhere.
- blackandblue 7y agohad extremely good experience with microsoft documentation. and i never did .NET. even old win32 API stuff still works, unlike many APIs i know of...