However, there are times when clicking on the shape doesn't show anything that looks incorrect. If that wasn't strange enough, there are times when the orchestration will compile even though it shows the error in the orchestration designer. And stranger still is something that I just noticed -- when I took out a send shape immediately following the Expression shape, the orchestration would no longer compile.
I have found 3 possible causes. This isn't intended to be an exhaustive list:
- This seems to occur most often when I try to wrap a string onto more than one line by using the "+" operator.
- In the orchestration view, one of the items will show an error. This should be pretty easy to fix from the orchestration view.
- Variables with identical names are declared in more than one scope. I'm not sure why this is a problem, but it does seem to be sometimes.
orchName = Microsoft.XLANGs.Core.Service.RootService.ServiceId
Thanks to Scott Colestock for pointing this out. He suggests using the following code instead: