title: Does UWP's .Net Native together with asynchronous programming make obfuscation irrelevant?
body: <p>I've read <a href="https://blogs.windows.com/buildingapps/2015/08/20/net-native-what-it-means-for-universal-windows-platform-uwp-developers" rel="nofollow">this blog</a> (and readers' comments therein) with interest and it highlights UWP's binary compilation -- intended to boost performance -- but at the same time playing part in making reverse engineering difficult due to binary compilation. On making reverse engineering difficult, I have also come across various comments alluding to how the the async/await asynchronous programming plays an important role in obfuscation (but not seen a detailed analysis on the subject to quote as a reference). I have also noted an interesting kinda <em>thought-provoking argument</em> <a href="http://www.preemptive.com/blog/91-dotfuscator-ce/net-native-what-s-it-mean-for-obfuscation-and-dotfuscator-in-particular/824" rel="nofollow">here</a> which makes these evolving programming technologies even more interesting.</p>
  
  <p>Does <strong>UWP .Net Native</strong> with <strong>asynchronous programming</strong> make <strong>obfuscation</strong> irrelevant? <s>Can we feel that a plain UWP apps's intellectual property protection (IPP) is as good as a non UWP app with 'good' obfuscation?</s></p>