Building Software using the Microsoft Tag API


A recent chat with Ken Levy from Code magazine, inspired me to write this multi-part blog on Tagging.
Microsoft Tag is Microsoft’s answer on the growing adoption and use of QR codes. While QR codes are a common technology in Asia, the people in Europe (and as I understood also in the US) are getting up to speed with the technology right now.

For the people who don’t know what a QR code is, a small introduction can be helpful to understand it’s potential. Microsoft describes a Tag as: “a new kind of bar code that connects almost anything in the real world to information, entertainment, and interactive experiences on your mobile phone. Tags are free to create and use. You can add them to your ads, posters, product packages, display it on your website, billboards, clothing…” (source: http://tag.microsoft.com )

To be able to use the Tags, people need to download the Microsoft Tag reader app by downloading it from http://gettag.mobi (browse to this site using your mobile phone).  When a tag is scanned, the phone will open a webpage, download a v-card, receive a text message, or dial a number.  Microsoft provides a ready to use Tag manager, but in some cases you would like to create Tags programmatically.

Microsoft lets you register for the tag manager and you can get access to their API, which is actually a WCF service. Although this is great, some things need to be overcome to work efficiently with the API. The API lets you create, manipulate and retrieve single tags. It is however, not possible to search or delete a Tag using the API.  Although this might sound as a big disadvantage we can turn it around and make it into an opportunity.

The “missing” functionality in the API forces developers to create local storage to make the tags searchable. By choosing the right Architecture and technologies we can develop a flexible implementation of the API which can connect to any Storage with minimal effort.  This blog consists of four parts, where every part will present a solution or approach to work with the API.

Part 1. Harnessing the power of IExtensibleDataObject
Part 2. Wrapping the service in the Repository Pattern
Part 3. Reading the .Tag format
Part 4. Decouple the Persistor with Dependency Injection

Tagged

5 thoughts on “Building Software using the Microsoft Tag API

  1. stacey says:

    Hello I would like additional information regarding the API for Microsoft tag.

    Thank You

    • dgcaron says:

      HI Stacey,

      What kind of information are you looking for? The API is self explanatory once you have referenced it in one of your visual studio projects. I know there has been some effort (by the community) to create a RESTFULL interface as well. if you browse around the community (which can be found by browsing to tag.microsoft.com, in the top right corner) i am sure you’ll find tons of stuff. if you need more information on how to use the API smart, then stay tuned for the next parts of my blog!

  2. […] This post was mentioned on Twitter by Marcel Kempers, dgcaron. dgcaron said: Multi-part blog post: Building Software using the Microsoft Tag API – http://wp.me/pScmH-S @microsofttag #microsofttag […]

  3. bet365 says:

    hello I was fortunate to seek your subject in google
    your post is marvelous
    I get a lot in your theme really thanks very much
    btw the theme of you site is really exceptional
    where can find it

  4. As i genuinely like the things you publish here. Extremely unusual and even brilliant. 1 dilemma however. I’m operating Chrome through Debian and even pieces from your up-to-date theme articles is a modest wonky. As i notice it’s a fantastic normal put together. However it’s a little something to help you preserve in mind. As i hope going without shoes will certainly allow and even continue to keep up the top high-quality authoring.

Leave a reply to dgcaron Cancel reply