Anyone ever cut n pasted an orchestration then modified it resulting in a ruined odx? The compiler throws erroneous errors relating to expression shapes that are in fact valid and messages not being constructed that are constructed. Change the type name on the orchestration, compile, then change it back. This will force Visual Studio to compile the XLANGs from scratch instead of using the broken XLANGs in the odx.
Another trick that I can’t beleive works is to go to one of the failed expression shapes and add a couple of empty lines. Then save the odx and compile. This seems to work around the issue consistantly. Once compiled you can then go back to the edited expression shape and remove the empty lines.