Hi all,
I'm trying to wrap my head around why this piece of code in my Automation Script is causing build errors. It's only happening from Cube, in Visual Studio it builds fine.
I've defined a Property class that has a Scope (string) property. Whenever I try and access that property I'm getting the following build error from Cube (DM 10.6.5).
"Property, indexer or event 'Property.Scope' is not supported by the language; try directly calling accessor methods 'Property.get_Scope()' or 'Property.set_Scope(?)'".
If I then update the script from cube to use the get accessor in this case, the script compiles fine. But if I do the same in Visual Studio, then my build fails because I cannot explicitly call an operator or accessor. Can anyone confirm if this is an issue with Cube?
Kind regards,
Hi Tom,
It is referencing a DevPack, using file exploerer and checking the properties I'm seeing product version 1.7.0-WFD-alpha002+837e0ed5c37627744df56b3cebecbce18d8b8b81, which is the same as the one being used by SLAutomation (checking the about pages of MediaOps)
I solved it. if I changed the code to access another property, other than Scope, then the script does not report any errors in Cube.
Looking further into that class, I can see that the Scope property makes use of the init keyword.
Once I changed that init to set, created a new build of the DevPack and redeployed the package to my agent, I had no issues anymore.
TL;DR don't use init (see: The init keyword (C# Reference)), the compiler shipped with DM doesn't support it.
Hi Thomas,
Is it possible that the DMA is using an older version of the DLL that doesn't include that property yet?