Hi,

>>My guess is that it has been fixed in an internal build and we'll see it in an upcoming CTP.
>
>Ah, well, that would be good news.
Partially good news. If true then it also implies that there is no workaround available for the current release......
Regards,
Viv