Folks, is anyone using the Cosmos DB Graph API? I just resurrected a demo I had working a few months ago, updated to the recent packages and ran it, every query run now produces:
System.MissingMethodException : Method not found: 'Double Microsoft.Azure.Documents.Helpers.GetHeaderValueDouble(System.Collections.Specialized.NameValueCollection, System.String, Double)'. I've now spent over 3 solid hours trying everything I can think of to get it working again, but without hope. I've twiddled config redirects, changed dozens of package versions in a wild variety of ways (including back to the ones from months ago) and tried all sorts of Gremlin queries, but absolutely nothing changes the error. Web searches produce zero matches. I thought I'd ask here just in case someone has seen this. I should point out though, that I'm really impressed by graph databases in general and see them as a fabulous alternative to RDBs for many realistic scenarios. I watched a good video yesterday by a chap who used a music collection database as an example where he tried to normalize it and finished up with dozens of tables and queries crammed with joins, whereas in a graph DB it was simple and natural. He points out quite rightly that if your find yourself making RDB queries with joins everywhere then you may be using the wrong database! Yesterday I watched about 20 Microsoft videos from conferences and tech announcements (some from Conf 2018), and now my brain is imprinted with images of smiling evangelists and product managers in blue shirts telling us how happy we are and how wonderful the future of software development will be. I must be living a different dream, because on the ground here all I get is compile errors, deploy fails, incomprehensible crashes, files not found, missing resources, package conflicts, authentication failures, assembly load errors, beta releases, breaking upgrades, software that won't install or uninstall, binding errors, Blazor, JavaScript, HTML, Xamarin and the bathroom drain keeps clogging up. *Greg K*
