There is considerable uncertainty around Windows phone. I would like to talk through some of that. And I would like to evaluate if Windows phone is still a good choice for me. Not you, me. I am thinking out loud here, hoping my thought process will help you as you contemplate switching to or from Windows phone.
Monday, July 11, 2016
If you are like me, you might spelunk from time to time in the bowels of your application's manifest file. But, "why?", you might ask, "Isn't everything in the manifest revealed in the graphical editor in Visual Studio?" Oh, you poor child. Allow me to enlighten you on this one: No.
One such setting is the <TargetDeviceFamily /> node, the child of <Dependencies />, the child of <Package />.
You can find it documented on MSDN where it provides this illuminating prose: "Identifies the device family that your package targets." There are some examples, sure, but I wanted to take a moment and make it painstakingly clear. I want to remove any doubt and leave you with the confidence to look at your manifest and edit it without fear.
Fact is, you set this when you create your project. The dialog above appears when you create a new Universal Windows Platform app. It's asking you the Target and Minimum version. But, of what? It is setting the initial versions of the "Windows.Universal" target device family.
Wednesday, April 27, 2016
Monday, December 28, 2015
Sunday, December 6, 2015
Check these out!
- A Developer's guide to Visual Studio 2015 Update 1 & all the Connect(); 2015 announcements by Jerry Nixon
- Visual Studio Code goes Open Source by Jeremy Foster
- An Intro to Visual Studio Dev Essentials by Adam Tuliper
- What's new with VS Subscription by Daniel Egan
- Visual Studio 2015 IDE Improvements by Paul DeCarlo
- What's New with Application Insights by Bret Stateham
- Visual Studio Tools for Apache Cordova by Adam Tuliper
- New C# REPL and scripting capabilities by Bret Stateham
- Visual Studio Code supports Extensions by Jeremy Foster
- HockeyApp in VS Team Services by Daniel Egan
- Understanding ASP.NET 5 & .NET Core by Adam Tuliper
- XAML Behaviors and Visual Studio 2015 by Jerry Nixon
Tuesday, November 17, 2015
What’s new for everybody but developers?We might as well get this out of the way. It’s good to be aware.
Tuesday, September 1, 2015
About a month ago, I was in the camp of rolling my eyes at hybrids on the road. To me their motivation was to save the planet. Well, it’s a big planet and a few hybrids aren’t going to supplant the egregious impact of a single volcano’s eruption. But then I started calculating my monthly spend on gasoline. My oversized sport utility vehicle and my turbo-charged crossover were fun, but expensive.
It’s easy math; a hybrid with a pathetic 13-gallon tank can drive farther than both of my other cars combined. Even though nothing is really created equal, hybrids have advanced enough generations for most to be similar enough that the brand you buy is mostly preference and price. I do some serious driving, so I decided to treat this adventure like a science experiment.
Wednesday, June 3, 2015
There are several controls that ship for free in the Visual Studio XAML toolbox. One of them is the ProgressRing, a neat, animated ring of dots that goes round and round and round. Developers use the ProgressRing to indicate to the user that something is working, loading, or just doing something where the user should wait.
But what if you wanted to do more without splitting the atom? Could you build your own, custom progress in that super-charges the branding of your Windows app?
Friday, May 1, 2015
Holy Moses, I’ve been published in MSDN Magazine!
You have lived to see it: a single Windows OS that can run across every type of Windows device. It has a single device platform to enable true universal hardware drivers and a single application platform to enable true universal Windows apps. Years in the making, this is a significant engineering accomplishment.
At the OS level, this means a single, maintainable and agile code base. For developers, it provides a unified, reliable API surface across every Windows device, from Internet of Things (IoT) devices such as Raspberry Pi to phone, Xbox, tablet, Surface Hub, laptop, PC and more (like Microsoft HoloLens). As shown in Figure 1, it’s a write-once-run-everywhere promise delivered in Windows 10 with the universal application platform (UAP).
Thursday, April 16, 2015
The patterns & practices team has been working on developing Azure architecture guidance. We’re happy to announce that first round of guidance is now available to public at https://github.com/mspnp/azure-guidance. The purpose of this project is to provide architectural guidance to enable developers to build and deploy world-class systems using Azure.