<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Universal Windows Project on DVLUP</title><link>/en/tags/universal-windows-project/</link><description>Recent content in Universal Windows Project on DVLUP</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 27 May 2015 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/universal-windows-project/index.xml" rel="self" type="application/rss+xml"/><item><title>One XAML for UWP, Windows 8.1 and Windows Phone 8.1</title><link>/en/blog/2015.05.27-one-xaml-for-uwp-windows-8-1-and-windows-phone-8-1/</link><pubDate>Wed, 27 May 2015 00:00:00 +0000</pubDate><guid>/en/blog/2015.05.27-one-xaml-for-uwp-windows-8-1-and-windows-phone-8-1/</guid><description>&lt;p&gt;I was recently involved in a conversation on how to have the easiest way to maintain a XAML view across a UWP (Universal Windows Project) a Windows 8.1 and Windows Phone 8.1 projects. There are a few options and the most straight forward way to do it with a UserControl residing in a Portable Class Library. However&amp;hellip;&lt;/p&gt;&#10;&lt;p&gt;What if you wanted to have **tailored code for each **without littering your code with #ifdef but still share a XAML view?  The XAML View might be what you&amp;rsquo;re looking for. This is a tutorial on how to do just that. An example project is available for download at the end of the article. Let&amp;rsquo;s get started:&lt;/p&gt;</description></item></channel></rss>