December 7, 2021

BUILD 2015 Summary: Introducing the Windows 10 App Model




//BUILD/2015 wrapped up last Friday, during the three day conference, a lot of news came out, but the important questions, like how to develop for Universal Window Apps, don’t find answer easily in the media. They don’t have time for these. I am afraid most developers can’t find time either. If you do, I bet you don’t want to watch those long, boring videos from BUILD. I am not sure if people are aware why those technical speeches are boring. I tell you why: 1. Most of technical speakers are not good speakers. If you don’t believe me, pick some of the links from here, see if I am right. 2. Listening to technical speeches is like your brain running a marathon, that’s very truthful, you just don’t realize it. Think about it, the speaker had run the content many times in his brain, so he talks at ease. But the listeners has to digest a very challenging topic very fast to catch up. I found this truth: it takes each listener 10 times brain energy than the speaker to catch up what he is saying.

Any way, I will do the listening for you, after that I write down some key points from the video. For some important ones, you’d better watch for yourself, for some, you can skip the video, just read my notes. I will put he notes after the video.

This is the first one, generic things about Universal Windows Platform App Model. Mostly concepts. As always, forgive my typing errors.


>> Project Centennial: Converting Classic Windows apps to run on Universal Windows Platform
Interesting topic. I haven’t heard of this. So, what is an classic app?

Classic Windows App: Every program that is not Windows 10 Universal App, or previous Windows and Windows Phone app. They include Win32 applications, .Net applications, WPF or Windows Form applications, etc.
A classic Windows app is wrapped into AppX for deployment, just like UWP apps.
1. AppX is the deployment model
2. Better way to install/uninstall/update
3. Runtime isolation registry/disk access
4. Enforce App Model Policy
5. Integrate into new app model
Three things make this happen:
a. Registry keys are stored locally to the app folder.
b. Take advantage of some UWP feature, like Cortana. (How?)
c. Windows Desktop App Model Policy: Allow Full API access and existing Desktop app lifecycle. Not allow access of drivers, NT services. No admin elevation, shellExtension
AppX: supports 150G
>> Developer Unlock: just an setting options from control panel.
Limit: 20 apps, Desktop: no limit
Debug can be done on WIFI.
(not working yet)
>> Install apps on removable storage
encrypted, options in manifest
>> App Resume Policy: (30:34)
All UWP apps will resume by default
All 8.1 phone apps and 8.0/8.1 desktop apps also resume
WP7.x and 8.0 apps do not resume (he said reason is for compatibility, those apps assume new instance. I think he is wrong, but…)
>> App to App/App Service
Cortana/People app for example
* I don’t real understand this yet. Is this like background tasks, like camera task. Looks like you create and publish App Services in your app, and other apps can call it.
>> Adaptive Tile Template – there are many templates for different need. Nice.

>> Utilize notification and action center

Not much details.


HoloLens FOV – What’s Next

HoloLens – The Matter of FOV

Register for: A Developer’s Guide to Windows 10

Jerry Nixon: “Why you must build a HoloLens app”




Microsoft’s Developer Evangelist Jerry Nixon wrote a blog post: Why you must build a HoloLens app, on March 27th. I don’t know how, but I missed it. Today, I am reading his blog together with you. I will also try to read between his lines, hopefully we can get something we didn’t know before.

I haven’t watched Channel 9 videos often recently, so, I am not really familiar with Jerry. Only know him after watch his Developer’s Guide to Windows 10 Preview (with Andy Wigley). Andy has been a regular on Channel 9. Anyway, important thing is Jerry is from Microsoft, and he know pretty much everything regarding Microsoft’s plans in UAP and HoloLens development. It all depends on how much he is allowed to say. We know he can’t say too much before April 29th, but as long as he is talking, we can heard something from his tune, or guess some lines that are not printed.



Regarding HoloLens programming, He said,

On top of all that black magic is HoloLens, introducing a new set of holographic APIs for app developers. Though it leverages Windows Core and though it leverages UAP, the device-specific APIs that enable the holographic experience are going to be different to what app developers do today. This means developers can use what they know, but will need to learn this new paradigm.

This means when we develop for HoloLens, it still follows UAP scheme. You create an UAP app (I don’t know if there is other choices in for Windows 10). You probably also add “HoloLens Extension”, if such thing exists. Basically there are things we already know: like coding for UAP, and things we don’t know: like HoloLens related APIs. HoloLens APIs is very much already in Windows 10 preview, but Windows 10 SDK doesn’t yet include HoloLens. I am sure we will see that during BUILD.

HoloLens is going to be a commodity. That means it is going to be cheap (which is relative, I know). When you include HoloLens in a solution, you aren’t including an investment in some strange, proprietary whatever. You are just including HoloLens, with a standardized version of Windows, a standard application model, with standard languages and APIs, and everything you can expect a development team to already know or easily learn.

Well, I don’t want to read too much. But when he put HoloLens and commodity in same sentence, I can’t stop speculating. Did he just said HoloLens is going to cheap or develop for HoloLens is going to cheap, or both? He did say: HoloLens is going to be a commodity. Take a note, please.

Don’t let HoloLens become a specialty skill. You are going to find the SDK just like every other Microsoft property. It will be standard and asynchronous, full of controls, methods, and classes.

Ok, it’s going to be asynchronous, like any WinRT APIs, but what those controls look like is interesting thing to find out. Obviously they are different from regular controls we do in XAML for PC and phone.


UAP, HoloLens, Recommended Readings – Developer’s Collection


Visual Studio 2015 to Release This Summer




Today, through The Visual Studio Blog,  Microsoft announced that Visual Studio 2015 to release this summer.

Today, we’re announcing the editions of Visual Studio 2015 that will be available when we release the final product this summer.

What is it?

Visual Studio 2015 will be released this summer. Reasonable guess is around same time of the Windows 10 release(this summery too), likely July, possibly August. Also VS 2015 will have three SKUs, instead of four. They are Community, Professional and Enterprise. If you are talking about Visual Studio at work, most companies deploy new Visual Studio a year or two after release. So for most developers, you are looking at Community Edition. I have been using VS Express Edition, which is called Community Edition now, never feel any limitation.

Why should I care?

I am pretty sure the only way to develop Windows 10 application is through Visual Studio 2015 or later. Visual Studio is on CTP 6 now. Please check here on how to setup Visual Studio CTP6 and Windows 2015 Technical Preview SDK.