Using the updated Default House Ad Implementation

Coordinator
Dec 27, 2012 at 5:11 PM
Edited Dec 27, 2012 at 5:26 PM

After a few issues we've changed the default House Ad implementation to accept a string instead of an Object, in extended testing and use it was found that passing an existing XAML object to AdRotator caused infrequent crash issues.

The new implementation we feel is more robust and more flexible and with the last update we also now support putting your house ads in a separate library or project.

To configure the latest option simply provide either a "DefaultHouseAdBody" setting in XAML or set a secondaryID in the configuration XML for the HouseAd to:

<namespace>.<object name>

For example in the test solution we set the default house Ad that is in the same project to:

AdRotatorExample.MyDefaultAd

And to alternately use the Ad in the separate class library we set it to:

DefaultAdSolution.MyLibraryHouseAd

So long as the local XAML is in your project and referencable it will be available.  We've also tested thoroughly that if it cannot find it for any reason it will fail cleanly and just disable the house Ad.

As before if you also provide a Remote House Ad URL that will take preference unless it is unable to download it.

 **Note The XNA implementation remains unchanged at this time because it uses a texture and not XAML

Ay issue please let us know.