So, just to recap, I’ve just embarked on my Gadgeteer journey (with a Spider), and decide to opt with Beta NETMF 4.2 as the starting point. First hiccup for me was the VS Designer, then my Wifi module (but that’s ok, resorted to the J11D), now… in talking to Azure and going through authentication and needing SSL (E_CLR_NOT_SUPPORTED)… I think I’ve come to a crossroads… Do I go back and start with NETMF 4.1 on my Spider, or sit it out for 4.2. Is it days or weeks away ? All advice gratefully received.
Dave, sounds like your trying to use a method that is not supported by NETMF. VS will catch most of that sort of thing at compile time but I have seen a few things that are valid in the full .NET but not in NETMF sneak through the compile process and fail at run time. Maybe posting your code (a simple example that shows the problem) would help.
It fails inside the GetRequestStream (). I’ve changed nothing, although I’m using my own Client credentials. There’s also a .NET Framework version which works fine, so that sort of demonstrates my credentials are ok. I can PM you my credentials if you want to have a go…
Read a Gus note on another thread that said “Have you set a encryption seed with MFDeploy”. Nope, I hadn’t. I have now, and we’re all good on the SSL code… I get some response back from Bing now… although it’s not playing on the music module yet… nearly there…