We are aware of such issue. Rather fortunately, it was immediately fixed in our very latest internal build (2014.1.0317). Can you please try with this version and let us know how it corresponds to your needs?
Please excuse us for any inconvenience caused.
DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.