Tried using the 2016.1.2 client with the same problem, then upgraded both client and server to:
Cache' Studio Client 2016.2.0 Build 721
Server Cache for UNIX (Apple Mac OS X for x86-64) 2016.1.2 (Build 206U)
The result is even worse from my perspective. Studio still complains about the same syntax, but now has a problem with the .$methods that are legal in 2016.1
Cache' Studio Client 2016.2.0 Build 590
Server Cache for UNIX (Apple Mac OS X for x86-64) 2016.1 (Build 656U)
I'm getting errors in Studio and from the compiler using this syntax - the errors don't actually seem to block anything, and the macro substitution works fine.
this line is flagged as an error:
and compiling gives:
ERROR: Core.Tube.Utils.cls(62) :DO or JOB given a property as argument set
Compilation started on 08/30/2016 10:26:49 with qualifiers 'ckb'
Compiling class Core.Tube.Utils
Compiling routine Core.Tube.Utils.1
Compilation finished successfully in 0.287s.
Bill, understood.
Benjamin, That's the conclusion I'd come to - the best option of a lot of bad ones.
Ouch, this really hurts, but I do see the need.
It's a lot of work whatever approach I take.
If only you were providing a transition with both forms being valid for a period - I'd still have the work to do, but I could spread it out to minimise the pain.
Given that the Azure pricing for storage contains a transaction element, is there any indication as to how many of these transactions will be consumed opening or saving an object as well as other common actions - obviously a simple object will use much less than a complex one.