Is the scripting application allowed in the Windows Store?

Question

So, I have this bit of a project planned for the Windows Store and Android. Basically, a networked multi-tool combined with a scripting mechanism for implementing protocols and behavior. Ideal use of things like "my embedded device uses this simplified network protocol. I would like to quickly prototype the way it is controlled from my tablet."

I understand that the Android market should not have any problems with this. However, the Windows Store policy includes a vague proposal to execute remote code.

3.9. All application logic must come from the application package and be in it. An application should not attempt to modify or expand packaged content. Through any form of dynamic inclusion of code or data that changes the application interacts with Windows Runtime or behaves with pay attention to the policy of the store. This is not valid, for example, load the remote script and then run the script in the local context of your application package.

Of course, the script engine will be isolated from the sand and it should be “safe” (completely intuitive, without reflection), but does it violate this policy?

Answer 1

If you create a scripting engine and run only local scripts, you will be good. However, if you were considering having a repository of scripts that could be downloaded and subsequently launched, this would violate the policy, as we understand it.

Answer 2

Unfortunately, I do not think that anyone other than someone from this team can answer this (or someone with direct experience in this) because of their proximity to the legal language. Have you tried the Windows Store Appl Publishing forum at: http://social.msdn.microsoft.com/Forums/en-US/windowsstore/threads

Answer 3

In the context of the given example script scenario, if the application does not change the scripting mechanism after deployment on the user system, so that the protocol / behavior representation (script artifact format) is changed, then this will be a policy violation. It is as if you are sending a Python interpreter, and at some point in time it abruptly switches to interpreting ecmascript.