Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I had the same issue and wrote a <a href="http://whiletruecode.tumblr.com/tagged/Windows-Phone">blog post</a> about it. Here's the important stuff: </p> <p>The symptoms of a problem with the SDK's <code>AdControl</code> seem to be pretty consistent: The page loads, the control flickers briefly, showing the hint of a 1 pixel frame, and then, <em>poof</em>. It collapses into nothingness, leaving only a black hole of dispair. </p> <p>In theory, setting up the <code>AdControl</code> is simple. The <a href="http://msdn.microsoft.com/en-us/library/advertising-mobile-windows-phone-7-visual-studio-designer%28v=MSADS.20%29.aspx">documentation from Microsoft</a> outlines the basics:</p> <ul> <li>Download and install the <a href="http://www.microsoft.com/download/en/details.aspx?id=8729">Microsoft Advertising SDK</a>.</li> <li>Add a reference to <code>Microsoft.Advertising.Mobile.UI</code>.</li> <li>Drag the control onto the page in the Visual Studio designer.</li> <li>Set the <code>AdUnitId</code> and <code>ApplicationId</code> properties to either test values or actual live values, which you can obtain from Microsoft pubCenter.</li> </ul> <p>But it couldn't be that easy. I followed the documentation carefully, but nothing was working. I couldn't even get test ads to show up, which seemed really weird. I even reverted to an older version of my app (yay source control!) and dropped in the new .dll. Failure.</p> <p>Finally, I found a clue in an <a href="http://community.microsoftadvertising.com/forums/p/69880/102113.aspx#102113">obscure forum post</a>.</p> <p>The Microsoft documentation neglects to mention several important details. You need to pay particular attention to the following if you're upgrading an existing project to the Mango ad SDK, as I was: </p> <ul> <li>You must specify a height and width for the <code>AdControl</code>. Failing to specify the <code>Height</code> and <code>Width</code> attributes, or setting them to <code>auto</code>, will cause tears of frustration. I'd recommend 80 pixels high and 480 pixels wide, as that's the native size of the ads that Microsoft serves up.</li> <li>It seems that you can't have two <code>AdControls</code> on the same page, or at least not in the same parent element. The second one will collapse. There might be a way around this, but I discovered it while building my demo app and didn't care to pursue a solution. </li> <li>You must must must specify certain capabilities in your <code>WMAppManifest.xml</code> file. Since I was upgrading my app, I didn't have some of the newer capabilities declared. The one that was causing all the trouble was <code>ID_CAP_IDENTITY_USER</code>. The following capabilities are all required for the control to function correctly: </li> </ul> <blockquote> <pre><code>&lt;Capabilities&gt; &lt;Capability Name="ID_CAP_IDENTITY_USER"/&gt; &lt;Capability Name="ID_CAP_MEDIALIB"/&gt; &lt;Capability Name="ID_CAP_NETWORKING"/&gt; &lt;Capability Name="ID_CAP_PHONEDIALER"/&gt; &lt;Capability Name="ID_CAP_WEBBROWSERCOMPONENT"/&gt; &lt;/Capabilities&gt; </code></pre> </blockquote> <p>Hope that helps!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload