StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The answer is basically no. You need to publish both a 7.0 and 7.1 version but they don't have to be separate apps as you can have 7.0 and 7.1 published versions of the same app. This was announced on the <a href="http://windowsteamblog.com/windows_phone/b/wpdev/archive/2011/09/20/submit-windows-phone-7-5-apps-today-update-7-0-apps-in-october.aspx" rel="nofollow noreferrer">Windows Phone Developer Blog</a>.</p> <p><em>[Edited to explicitly state that I am not advocating faking features]</em></p> <p>If you still want to target 7.0 you have some options.</p> <ol> <li><p>Have separate 7.0 and 7.1 projects.</p></li> <li><p>Have one solution that shares code between two projects using <a href="http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2010/01/20/linking-files-in-visual-studio.aspx" rel="nofollow noreferrer">file links</a>, one targeting 7.0 and the other targeting 7.1 You should be able to share a lot of code and perhaps pull visuals out into user controls that could be shared.</p></li> <li><p>If you really want <em>one</em> app, <strong>though I don't think it's a good idea</strong>, there is a possible workaround using the <a href="https://stackoverflow.com/a/8732821/269608">answer from this question</a> which might let you use secondary tiles. </p></li> </ol> <p>Along with option 3, you could probably also fake fast app switching by only handling tombstoning in certain situations with something like this (off the cuff, not tested):</p> <pre><code>bool isNewInstance = false; public PageConstructor() { isNewInstance = true; } override OnNavigatedTo() { if (isNewInstance) { // handle page set up as necessary } else { // handle tombstoning if necessary } isNewInstance = false; } </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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