24-11-2014, 03:11 PM
Sorry, we tried several times to find out why this feature is not working anymore - today I did it again and find the solution - .NET 4.0 caused that error... and it is fixed - will be available in the first patch - I want to wait some days for more feedback and then we will publish the first patch...
Regards/Gruss
Oliver
Oliver