Grow your business by advertising on MSN, Xbox, and more!
Hey folks,
Good news for XAML Publishers! We have a new version of the SDK (available here) which remediates z-index issues.
Previously, we had asked XAML Publishers to work around the z-index issues using isPerformanceScrolling=true and Suspend/Resume APIs.
The new SDK introduces a new initialization time property for the XAML AdControl called useStaticAnchor. When set to true, the SDK will always use the WebviewBrush (WVB) to render the ads instead of the WebView (WV)
control that has the z-index issues. The experiences have been updated to render interactive anchors inside the WVB.
Some callouts:
· If UseStaticAnchor is set to true, Suspend/Resume/IsPerformanceScrolling will not try to switch between WVB and WV
· If UseStaticAnchor is set to false, Suspend/Resume/IsPerformanceScrolling will behave the same way as before this feature is implemented
For developers that don’t use XAML, there are no significant benefits to downloading and installing the new Ad SDK.
Please remember that you must resubmit your app to WindowsStore whenever you update the Ad SDK.
Cheers,
Ian
Follow us on Twitter @MSAdvertising | Find us on Facebook and YouTube | Share your thoughts in the Forums | Subscribe
I've set UseStaticAnchor to true, but now at Runtime ads are non more clickable, is it the right behaviour? Did I make any mistakes?
Thank you! Now I can use the ads again! I have noticed that UseStaticAnchor="True" has to be set as the last parameter.
<UI:AdControl UseStaticAnchor="True" Width="250" Height="125" ApplicationId="..." AdUnitId="..." /> was not working
<UI:AdControl Width="250" Height="125" ApplicationId="..." AdUnitId="..." UseStaticAnchor="True" /> worked!