Windows Phone 8.1

Microsoft announced their latest version of Windows Phone, version 8.1, this new version is due out this summer and is compatible with all existing Windows Phone 8.0 devices. In addition manufacturers, such as Nokia, are coming out with new devices tailored to Windows Phone 8.1.

Regarding Windows Phone 8.1 the new features include Cortana, a new Notification Center, Enterprise VPN and Workplace features, among many new apps and app updates. Cortana looks really cool, she’s far more than ‘Siri for the Windows Phone’ as she’s been called. I like how she mimics a personal assistant and offers something unique in this world of privacy concerns, where she opens her ‘notebook’ and provides transparency about what information she’s tracking about you, such as likes, favorite places, and favorite people, which she calls your inner circle. You can also modify any of this information if it’s incorrect.

The Notification center is huge, it allows apps of your choice to provide a higher level of feedback to the user regarding content. I’m also excited about the Workplace features because it makes Windows Phone an enterprise ready device, not that it wasn’t already, but the new features, such as VPN, cover many more use cases that come up in larger organizations. Windows Phone has also been updated with all the power of Internet Explorer (IE) 11, including in-private browsing on the phone.

While Windows Phone 8.0 runs on the Windows Runtime (WinRT), there were many APIs, suchs as the camera APIs which were different between Windows and Windows Phone. Windows Phone 8.1 includes developer changes to make the APIs consistent and created a new style of WinRT apps for Windows Phone called Universal Apps.

Windows 8.1 Update

Windows 8.1 also received an update, which is already available on MSDN. This update includes visual updates, such as a Windows Store apps surfacing on the task bar, better mouse and keyboard support within Windows Store apps, and the addition of a power and search button on the start screen.

There is also new pricing around enterprise side loading of apps which makes it more economical to deploy internal Windows 8 apps. The final feature they announces was a feature called Enterprise mode within IE 11, which enables legacy functionality so those internal sites can still be compatible.

I’ve always loved the Windows platform and these updates make it that much more compelling. I really encourage people to take a non-biased look at Windows 8 if they haven’t done so already. They also leaked some secrets about unreleased features like a desktop Start Menu, yes menu, not Start Screen, and Windows Store apps running on the desktop in resizable windows. It’s nice to see Microsoft showing their hand to the community and being transparent.

Universal Apps

It’s been rumored that Microsoft was converging Windows Phone and Windows Store apps. At //build they announce a new app development template that makes this much easier. These new templates work for both .NET and JavaScript for new apps and, as they showed in the keynote, existing apps.

With the convergence of the Windows Phone APIs and Windows Runtime APIs Universal apps for Windows Phone and Store can share basically all of your app code and view code. But, it doesn’t stop there. Microsoft is using this Universal app template with the help of Xamarin to create apps with shared .NET code for iOS and Andriod as well.

While day 1 came many highly anticipated announcements about Mobile and Windows, I was expecting most of them because I follow that space so closely. The day 2 keynote offered new announcements that I wasn’t expecting.

Azure

There are so many updates around Azure that it’s hard to keep up. It’s hard not to be compelled by all the amazing Platform as a Service (PaaS) tools that are available for Azure. The big announcement for Azure was a preview version of a brand new portal, which surfaces pricing and monitoring right up front. Additionally, we have new .NET support for Mobile Services, a new traffic manager, and Web Jobs for Azure websites, some of which have been in preview mode and announced earlier. Brady Gaster and Joe Levy also announced, in their session, the deployment of a new Microsoft Azure Management Libraries (MAML) which provide a simplified .NET wrapper over the REST management services for Azure.

VS 2013 Update 2 RC

Visual Studio 2013 also received an update, currently in RC. This update comes with numerous Azure integration improvements to the Server Explorer toolbox, like the ability to create a VM directly from Visual Studio, or create an Azure website directly from the file new website wizard. Visual Studio 2013 Update 2 also adds all the juicy new Windows Phone 8.1 and Universal App Templates. Finally a really cool feature, which they also showed in the keynote, is the ability to sync your development environment with the F12 debugger tools of your browser (not just IE). This feature is powered by BrowserLink. Scott Hanselman and Scott Hunter have a great session describing these new features.

TypeScript

While TypeScript wasn’t really mentioned in either keynote, Anders Hejlsberg announced the version 1.0 release of Typescript in his session. Unfortunately I haven’t had a chance to use TypeScript much, but I’m following it closely and looking forward to an opportunity use it.

Roslyn

You can’t mention Anders Hejlsberg without mentioning C#, and the big announcement during the day 2 keynote was the open sourcing of the Rosyln project and the creation of the .NET Foundation. The C# compiler has been around for quite some time and, as you can imagine, the codebase has some technical debt that has made some new features extremely complex. Additionally most compilers to date are black boxes. For these reasons, they decided to re-write the C# compiler as a service with an open API. This makes the numerous syntax features from the backlog super easy, but also enables third party and even in house creation of custom refactorings and behaviors extremely easy to write.

While Roslyn itself it awesome, open sourcing it means that the community can closely watch any changes and discussions and even supply patches. They are even posting their internal meeting minutes for their design sessions. Follow it for yourself at http://roslyn.codeplex.com

Project N

There was another major announcement that wasn’t announced at the keynotes and that is ‘Project N’. It is a new preview for a project also known as .NET Native, which increases performance for .NET apps by running them thru a native compiler to pre-JIT and optimize .NET code into pure native code. Currently this project is in preview and supports C# for Windows Store apps on ARM and x64 only, but they’ve discussed expanding this in the future. See the FAQ for more information.

This year’s //build conference was really amazing for me. In addition to the numerous updates mentioned above, this year was a great networking experience for me personally. Since I was awarded my MVP this year, I’ve had a wonderful opportunity to meet so many new people, albeit virtually. The conference gave me an opportunity to meet these people face-to-face. It was also nice to see all the Microsoft folks. Overall a great event lots of content to follow up on, thankfully it’s all recorded online at http://channel9.msdn.com/Events/Build/2014.

The first step is to create an extended version of your ViewModel, in my case I created a folder called SampleData and added a new class called HubPageViewModelSampleData.cs

This HubPageViewModelSampleData class inherits from our HubPageViewMode and just initializes the sample data in the constructor.

public class HubPageViewModelSampleData : HubPageViewModel
{
	public HubPageViewModelSampleData()
		: base(null, null, null)
	{
		DisplayName = "Hub";
		Sites = new ObservableCollection<Site>()
		{
			new Site() {
				SiteName = "Site 1",
				SiteUrl = "http://www.example.com/123",
				Status="Online" },
			new Site() {
				SiteName = "Site 2",
				SiteUrl = "http://www.example.com/456",
				Status="Online" },
			new Site() {
				SiteName = "Long Site 1",
				SiteUrl = "http://www.example.com/123/abcdefg/456/hijklmnop.html",
				Status="Offline" }
		};
	}
}

If your base class has any dependencies injected you can supply a parameterless constructor override with null values or null implementations. You can also insert overridden methods/properties, which I would tend to prefer over injecting your ViewModel with a lot of checks for DesignMode.DesignModeEnabled. Once you have your sample data view model created you just have to wire it up to your view. In order to do this you’ll need setup the design time DataContext with a design time instance to this sample data view model.

<Page
x:Class="App.Views.HubPage"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:system="using:System"
xmlns:micro="using:Caliburn.Micro"
d:DataContext="{d:DesignInstance Type=sampleData:HubPageViewModelSampleData, IsDesignTimeCreatable=True}"
mc:Ignorable="d">
<!-- … -->
</Page>

Visual Studio supports this design context for DataBinding and will work if you use declarative {Binding} statements in your XAML. While this way doesn’t use Blend and it is still part of your deployed Appx, it is easy to setup. Unfortunately this won’t work with our project because we are using Caliburn.Micro. One of the great features of Caliburn.Micro is the ability to do convention based binding. This feature doesn’t use the declartive Binding syntax that the XAML designer is expecting. Because of this the bindings don’t work with the XAML for a Caliburn.Micro view. Luckily the team has provided an attached property that executes just the ViewBinding portion of the framework in design mode. This attached property Bind.AtDesignTime should be added to the same control that has you’re design DataContext as you can see here.

<Page
x:Class="App.Views.HubPage"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
xmlns:system="using:System"
xmlns:micro="using:Caliburn.Micro"
xmlns:sampleData="using:App.SampleData"
d:DataContext="{d:DesignInstance Type=sampleData:HubPageViewModelSampleData, IsDesignTimeCreatable=True}"
micro:Bind.AtDesignTime="True"
mc:Ignorable="d">
<!-- … -->
</Page>

With this in place we can see the effects of our design decisions right in the designer without having to run the app.

By following these steps you can setup sample data support for all your view models hopefully achieve the symbiotic moment you get from an effective developer/designer workflow.

The keynote centered around 2 main topics. First is the changes in computing, including hardware, mobility, and the way in which we interact with multiple devices of all sizes. Second, is the new Metro UI , which is the way in which immersive Windows 8 applications are built and developed to provide rich experiences on the native operating system.

Computers have been changing for quite some time, devices are getting smaller, they are responding to touch input, and customers are using them on the go. This means applications need to be built in a way that allows customers to interact with content in a performant way no matter the screen size. Customers are also using computers in all aspects of their daily lives. They need applications that are mobile and that actively synchronize themselves across multiple devices, so that the experience is seamless.

Touch is an extremely important aspect to all this, with former GUI technologies there were some affordances to lags in performance when using a traditional mouse input. When using touch as a primary input it seriously impacts the user experience if the application doesn’t respond to a gesture. Microsoft has stated that they are committed to increasing performance and with reports of an 8 second boot time, quick resumes through Connected Standby, and a decrease in overall operating system memory consumption to 281 MB of core OS memory (down from 484MB), it is apparent that they are really squeezing every byte possible out of the operating system.

Microsoft also announced a brand new line of computing devices from the small tablet devices (which were given out to all attendees) to large multi-monitor desktops which support touch and hardware accelerated graphics. Power users will also benefit from the new Hyper-V support which is now included in Windows 8. Another important hardware feature that was announced is the ability to Refresh and Reset your desktop settings to a factory state.

The Metro UI is much broader, while reimaging the entire Windows 8 application experience, they have also reimagined the entire application model in the form of new API that sits on top of the Windows kernel call the Windows Runtime. This new Windows Runtime (WinRT) is a brand new application model that is completely different than the previous Win32 model. It offers a fresh new Windows start screen with Live Tiles and Notifications. Applications can now interact with the entire screen real estate without the need for window management complexities like chrome, minimizing, etc. WinRT has built in support for Charms, which allow developers to communication across applications. The only bit of screen real estate consumed by the runtime is a single pixel around the entire screen which is used to invoke both system and application commands via a concept called “first pixel sensitivity”.

There has been a lot of talk about Silverlight and WPF developers getting phased out of the new Windows 8 platform, first off, this is not true. Windows 8 has committed to offering full backwards compatibility with Windows 7 and all the Win32 applications and frameworks which are built on top of it. This doesn’t mean Silverlight or WPF will work on WinRT. However, (before you get too upset), your skills as a XAML developer are not lost. WinRT has rebranded their previous UI frameworks into a new set of components, which you will find very similar, under the distinction of XAML (the UI markup language) and the model/controller language of your choice (ie. C#, VB, C++). They’ve also added to the WinRT the ability to create applications with a view markup defined in HTML5 and CSS with controller logic written in javascript. A move that will hopefully attract designers who were previously constrained to web technologies to come on board and start creating native applications for the windows 8 platform.

Since this is a “Developer’s Preview Release” and since so many changes were made to the application development and deployment model, Microsoft also announced the release of new version of Visual Studio 11 and Expression Blend. The hope is that developers will download the bits and start looking as ways in which they can reimagine their own applications. Everything presented today will be provided for developers to download at http://dev.windows.com.