$ 0 0 Moved your post to .NET SDK forum This is a known issue and R&D is working on it. Should be fixed in SP 17