Excellent! Thanks!Support Team wrote:To cut a long story short: This should be fixed with the upcoming version 3.0.1.
I'll wait for the fix rather than make the change to VS. Then I'll be able to dive in and start making all the changes to my code required by the 3.x breaks.