Is winrt code better protected against reverse engineering?

My application is being developed in silverlight. Plan to launch it this year. I am worried that my haps are being reverse engineered. I do have a ton of intelligence in my wcf service, but you can't put everything into the service. Now winrt is an option. The fact that both silverlight and winrt use xaml makes it possible to move my client code to winrt, but only if that code is reverse engineered. Opinions?

+3


source to share


2 answers


Not.



http://JustinAngel.net/ReverseEngineerWin8Apps

+3


source


There is little way to protect your code from reverse engineering. Working on the server hides the code that makes it the most secure, obfuscation still protects it well enough but not completely, and it has other risks. WinRT allows you to write your own code, which is slightly more difficult to process than .NET code, but only marginally . On the other hand - if your application is written in unminified javascript - you are basically submitting source code and you don't even have an xap file to unpack - just look in C: \ Program Files \ WindowsApps and there is a folder for your application where all files that you see in Visual Studio.

Then you can look at these parameters and decide which is best for you. Ultimately though - the choice between WinRT and Silverlight is a platform choice. WinRT apps will only work on Windows 8 and (we can assume) possibly the next version of Windows Phone, which, at least initially, limits your target audience. I haven't heard of the possibility of selling Silverlight apps through the Windows Store unless you're targeting Windows Phone, where that's the only option (that's XNA - both are .NET based).



If your client-side code is truly unique intellectual property, you better protect it with patents and copyright law than with obfuscation and compilation.

+2


source







All Articles