All Metro applications must be inspected before distribution through Windows 8 AppStore. Does this mean it will not be allowed to use code obfuscation? Or it is still possible, and only some specific aspects are going to be monitored during such inspection?
相关问题
- Inheritance impossible in Windows Runtime Componen
- Replacing or recreating a file in Windows 8 RT kee
- Draw waveform from MP3 stream in C# on WinRT
- how to disable caching HTTP GET in metro app, I am
- ListView in a metro app does not get its vertical
相关文章
- Show flyout using BottomAppBar
- New Windows Application - What language?
- Get English exception message instead of local lan
- How to remove an element from an IGrouping
- Exception when reading text from the file using Fi
- Protect Web API from unauthorized applications
- Progruard and R8 being deprecated - Android Studio
- HttpUtility.HtmlDecode in WinRT
Obfuscation is still possible for WinRT. The inspection made by the Application Certification Kit cover lot of aspects including metadata and IL verification. Just like the old peverify did.
Here are some facts:
Remember, if you have some logic that you want to hide, make a webservice and consume it in your client app. Better spend your time building better app, fixing bugs etc.
No dice, if someone has access to the binaries is just a matter of time when someone cracks it.
This is an armchair answer with some things that come to mind:
Even a C++ application can still be anazlyed if it depends on dynamic linking to a runtime or API, which is the case with WinRT applications. Microsoft approval can in theory include automated or human guided testing of your app using a special sandbox and/or OS hooks capable of detecting if your application attempts certain prohibited operations.
Under the hood, C++ apps for WinRT are more like native C++ apps than C++/CLI, so obfuscation is not needed to the degree that it is for C#, all things being equal.
You can still build C# apps that target WinRT, but your code will still be compiled to CIL and run within the CLR (more or less), invoking WinRT through wrappers that Microsoft provides. Because it's CIL, the question of obfuscation should be equivalent to that of C#/.NET obfuscation in general.