Which capabilities is required in the simpliest application to accept it on marketplace? [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 7 years ago.

Improve this question

like in topic: Which capabilities is required in the simpliest application to accept it on marketplace? I have the siply application which for example have 1 button and 1 textBlock and onClick event it display "Hello World!" in TextBox.

I have read specification of each capabilities on msdn and I this easy application doesn't need any of them. But if my application will be accept on marketplace if I submit it with empty Capabilities elements?

Thanks for all answers!

Answer 1

Run the capabilities detector and go with its suggestions for your settings.

From this link http://compiledexperience.com/blog/posts/windows-phone-7-capabilities:

"The latest update (October 2010) to the Windows Phone 7 tools provided a console application to detect the actual capabilities used by your application if later you want to edit your WMAppManifest.xml to that, this tool is under Program Files\Microsoft SDKs\Windows Phone\v7.0\Tools\CapDetect."

Official instruction link for the Capabilities detector here: http://msdn.microsoft.com/en-us/library/gg180730(v=vs.92).aspx

Answer 2

Edit - I read the title and most of the question, but didn't read the part about the Capabilities section

Since the question was about the "Capabilities" section of the manifest... one thing to keep in mind is that (at least for now), it doesn't matter what you put in the capabilities section. When you submit your app for certification, the process automatically scans your app and determines what capabilities are required, and puts them in the app manifest for you.

end edit

I'm not sure this is the best place to ask this question. You might want to try http://create.msdn.com - In my experience, though, they don't fail based on functionality, unless it violates the terms of use (e.g. copyright infringement, sexual themes). Mostly, they look to see that:

• The application works.
• It doesn't make use of any non-approved APIs
• It doesn't crash
• It handles the back button correctly

They also look at a few other things like:

• Startup time (less than 5 seconds), and
• Memory usage.

There are a bunch of other things that you should be familiar with as well.

The certification requirements, which can be found here are very clear in what they expect, and are pretty well written.