Hi Rainer,
Thanks for your patience!
After the discussing with our Dev team, the Engineer said there were some
reason leaded to the control didn't work well.
For the current scenario, I'm sorry that I think this is out of the
newsgroup services. It is better for you if one of our PSS support
engineers could work with you. This may need you submit a support incident
in Microsoft PSS (Product Support Service). As a MSDN subscriber, you have
two free support incidents. I think you can get the work around or the
specific hot fix for the current problem.
By the way, if the problem is confirmed by Microsoft PSS as a product
issue, PSS won't charge money. Every MSDN subscriber has two free support
incidents. You could use one of them to contact Microsoft PSS. So you don't
need to pay money yet. Surely if the issue is a product issue, you still
have two free support incidents.
For your reference, I attached steps to contact Microsoft PSS here: You can
contact Microsoft Product Support directly to discuss additional support
options you may have available, by contacting us at 1-(800)936-5800 or by
choosing one of the options listed at
http://support.microsoft.com/common/...gp;en-us;offer
prophone
Regards,
Yuan Ren [MSFT]
Microsoft Online Support