Capability Detection Inside Visual Studio 2010

For the last month or so I have been developing an application for my windows phone, that I am going to publish to the marketplace in the coming week(s). As I am getting ready to make the final build I have started searching the certification requirements and good practices. One that I had missed was the advice to use as few capabilities as needed in the WMApplicationManifest.xml

Fortunately Microsoft is distributing a nice tool with the Windows Phone SDK that performs the task of finding the capabilities that your application is using. The problem is that this is a console application that lives inside the C:Program Files (x86)Microsoft SDKsWindows Phonev7.0ToolsCapDetect folder (for those having x64 machines). It also requires 2 arguments to invoke, one of which is an xml located at the same directory.

Tired of having to execute the following command each time:

I decided to make a shortcut for myself from inside visual studio 2010. The process of doing this is extremely easy and I wonder why Microsoft did not put it there in the first place.

Tool configuration

Use this configuration

The two lines that do not show well in the photo should be:

When this is done, you can now invoke the tool from tools->Capability Detection or whatever name you gave it. The result is much better and easier to get to:

Capability Detection Result


Hello Blog

This is my opening blog post. Hopefully it is not going to be the last one. Through this blog I will try to give some insights to people about software, software engineering, hardware and pretty much everything that comes up in my work/life.

A few things about me first. I am an Electrical Engineer with an Msc in Nanosciences & Nanotechnologies who is currently working towards his PhD in Chemical Engineering. My interests revolve around software development, web development and electronics engineering. I am also a tech enthusiast and a new father. It is quite a mix, but it keeps me occupied and hopefully will give me something to write about.

I will try to put out things that baffled me, and their solution, so others (and probably me in the future) do not have to go through this again.