Microsoft Band is packed with sensors that let it track your workouts.
However, one sensor you don’t hear about often is the Skin Temperature
sensor. This sensor allows you to read the temperature in Celsius of your
skin where your Band is. There aren’t any apps built-in to Microsoft Band
that make use of it directly. However, as a developer you can take readings
from that sensor from an app on your phone using the Microsoft Band SDK
Preview. The SDK is very preliminary and you can only do a handful of
functions from a phone including reading the sensors, creating tiles and
sending notifications, and changing the theme and background image. It has
a direct dependency on the app you deploy to your phone. You can’t
actually build an app and deploy it so that it runs on Microsoft Band
natively. This limits you quite a bit, but you can still do a few cool
Originally posted on the MVP Award Program Blog on December 8th, 2014.
In the last year or so I have proudly referred to myself as a
“cord-cutter”. I’ve dropped my cable / satellite subscription in favor
of streaming services and an over-the-air antenna. When it comes to
streaming, of course the XBOX ONE excels with services such as Xbox Video,
Netflix, Hulu, Vudu, NBA TV and Amazon. How is that any different than any of
the many streaming devices out there such as Roku, Amazon FireTV, Chromecast
and more though? From a standpoint of streaming alone, there really isn’t
much dif... (more)
By now, you have heard about how the SharePoint 2010 development experience
has been improved. We can easily deploy web parts and other code without
having to manually manipulate any XML files. What about under partial trust
though? Many of you that know me know that I have pushed using Code Access
Security quite a bit through a series of blog posts and talks. So it would
be irresponsible of me not to talk about how we can do that in Visual Studio
2010. The good news is that it is a lot easier.
Let’s start by creating a new SharePoint project in Visual Studio 2010 and
SharePoint on Ulitzer
This is already starting to be an interesting topic, so I wanted to post
about it. We’ll start with the facts.
SharePoint 2010 only runs on 64 bit operating systems In the past, SharePoint
developers have pretty much always had to develop in a virtual environment
Windows Virtual PC does not support 64 bit guests but other non-Microsoft
virtualization technologies do SharePoint 2010 can run on Windows 7 / Vista
x64 Most developers do not want to run a server OS on their development
machine Some developers may still be running 32 bit operating systems (ack!)
With MOSS 2007, I often got asked what order do I install these solution
packages in. Oftentimes, it was critical that they get installed in a
particular order. With features, we have had the ability to set
dependencies, but we really didn’t have anything like that for solution
packages. Well, I haven’t heard people talking about this new feature
yet, but we can in fact set solution dependencies in the manifest.xml file.
The way it works is that it checks to see if a dependent solution has already
been deployed on your farm (or site collection for sandbox solutions).