My orchestration throws a Microsoft.XLANGs.BaseTypes.InvalidPropertyValueExc
eption. In the relevant scope I have a catch block of a type System.Exceptio
n, but exception above is not caught despite the fact that it is of a basic 
type System.Exception. What
might be the problem?

By the way, HAT reports the exception above as Microsoft.XLANGs.Core.Invalid
PropertyValueException. Why would that be the case?

Thanks.

[ Post a follow-up to this message ]

I found the reason. Assigning a string longer than 256 characters in the cat
ch block caused additional exception that I didn't expect.

What is the recommended way of fatching exception details (Message propertie
s) inside orchestrations for a freindly display if I want to avoid looking a
t HAT all the time, considering that Message usually exceeds 256 characters?

Thanks.

[ Post a follow-up to this message ]