SQLite for WinRT
Getting Started: Authoring HTML for Windows 8 Apps using Blend for VS 2012
Published by Kirupa on 30.08.2012 at 17:59
Almost two years ago, we set out on a path towards building a flavor of Blend that allowed you to seamlessly craft HTML, CSS, and JavaScript into Metro style applications. We are thrilled to announce that the final, released version of Blend is available for you to try out. As in previous releases, there is no more need to download Blend separately. It is now part of every VS download that targets any of the supported platforms. You can learn more from our launch blog post.
Download Visual Studio 2012 with Blend and Windows 8. MSDN Subscriber Downloads has several versions available, and there are free downloads available for non-subscribers.
Getting Blend installed and running is only one part of it. Using Blend in conjunction with Visual Studio to build great Windows applications is the other part, and that is where this post comes in. In this post, you will get an overview of Blend and the great features it provides for allowing you to build great Windows applications.
Hello World
What better place to start than with the classic hello world example. Learn the basics of the Blend UI and how to start working with the content creation and styling features you have available:Read the entire article here.
Window 8 DevCamp – Raleigh
Published by mattduffield on 20.08.2012 at 05:00
I had a great time presenting in Raleigh for the Windows 8 DevCamp!
As promised, I wanted to post a couple of references that you might find helpful in developing Windows 8 applications:
- Migrating apps from Consumer Preview to Release Preview
- Migrating apps from Release Preview to Windows 8 RTM
- Windows 8 Modern Style Apps
- Memory Game
- Programming Windows 8 Apps with HTML, CSS, and JavaScript
- White papers for Metro style apps
- Downloads for Metro style app development
- Windows 8 Keyboard Shortcuts
WinJS Custom Controls
Published by Corrado Cavalli on 21.07.2012 at 11:00
<div data-win-control="WinJS.UI.SemanticZoom" > </div>if you have pages (even in different applications) that need some special kind of functionality paired with some custom UI, custom controls allows you to reach the “write once, use everywhere” paradigm (unless you like reinventing the wheel of course…)Let’s see how you can create your own custom control and use it inside a HTML Metro application, simulating a simple custom countdown control.Step1: Design the user interfaceWhile not strictly a requirement I personally like to start from the appeareance of my control, so I fire up Expression Blend and start design it:
image-1I’ve highlighted the HTML representing my control’s UI and, on right side, associated CSS, question now is: how do we turn it in a WinJS custom control? Read the full post
Running User Code in the XAML Designer: Blend and VS 2012
Published by Harikrishna Menon on 06.07.2012 at 21:41
The XAML designer in Blend & VS is a projection of a running application (see Mysteries of XDesProc–Revealed!), but unlike a full-fledged app, usage of certain programming constructs and resources might cause the designer to crash or behave in an unexpected manner.
Note: This post and the examples shown are written in the context of the XAML Metro style app designer, but some of them apply to Windows Presentation Foundation (WPF), Silverlight, and Windows Phone designers as well.
First, a quick overview of what code runs in the designer and what doesn’t.
- The code-behind of the instances of user controls and custom controls in the active XAML page are run in the designer.
- WINRT or CLR types that you declare in XAML as resources are instantiated in the designer process.
- Events dependent on CoreWindow and Input events will not be fired in the designer.
Using [DependencyObject].Dispatcher
As the designer process is basically a WPF Application that hosts XAML runtime components, types like CoreWindow and CoreDispatcher are unavailable. CoreDispatcher is generally used to marshal an operation from a non-UI thread to the UI thread or schedule it for later execution on the UI thread. Since there is no CoreWindow in the designer process, CoreDispatcher objects in the designer will always evaluate to NULL. Hence, any user controls and custom controls that use this construct in their code-behind might not work correctly in the designer. When we detect that an instance of a user control or custom type cannot be created, we catch all resulting exceptions and wrap them in an error report linked to that specific instance, and continue creating the rest of the document.Read the entire article here.
SQLite on Windows 8
Published by Kenny Kerr on 21.06.2012 at 13:11
The amazing little SQLite database engine now officially supports Windows 8 Metro style applications. It sounds like this was done with the full endorsement of Microsoft so you should have no trouble including it in your Metro style apps and get the blessing of our friendly Windows Store custodians. I believe this covers Windows Phone 8 as well. Here is the news:
SQLite version 3.7.13 adds support for WinRT and metro style applications for Microsoft Windows 8. The 3.7.13 release is coming sooner than is usual after the previous release in order to get this new capability into the hands of developers. To use SQLite in a metro style application, compile with the -DSQLITE_OS_WINRT flag. Because of the increased application security and safety requirements of WinRT, all database filenames should be full pathnames. Note that SQLite is not capable of accessing databases outside the installation directory and application data directory. This restriction is another security and safety feature of WinRT. Apart from these restrictions, SQLite should work exactly the same on WinRT as it does on every other system.
Thanks D. Richard Hipp!
It’s Alive! – WriteableBitmapEx 1.0 for WinRT Metro Style, WPF, Windows Phone and Silverlight
Published by Rene Schulte on 14.06.2012 at 16:13
After a few preview versions, I'm happy to announce that the final version of WriteableBitmapEx 1.0 is now available.
A couple of weeks ago we added official WPF support and WinRT Metro Style support. With that WriteableBitmapEx is now available for 4 platforms: WPF, Silverlight, Silverlight for Windows Phone and Metro Style WinRT .NET.
You can download the binaries here or via the NuGet package. The packages contain the WriteableBitmapEx binaries. All samples and the source code can be found in the repository.
Since the last WinRT preview version, a new WinRT sample was added, a couple of bugs were fixed and a new FromStrean method was added which loads an image stream into a WriteableBitmap. The project was also updated for the Windows 8 Release Preview. Please read this blog post for more details (about the WinRT version).
Comparing Windows 8 Consumer to Release Preview
Published by Koen on 31.05.2012 at 23:25
Windows 8 Release Preview has been released today. Learn all about the latest Windows 8 preview release at preview.windows.com.
If you have been developing XAML Metro apps with Windows 8 Consumer Preview, you probably need to know what has changed in the APIs. The following link provides a complete diff list of Windows Consumer vs Release Preview;
LINK: Windows 8 Consumer vs Release Preview DiffList
Goodbye Windows Aero
Published by Kenny Kerr on 23.05.2012 at 14:39
Microsoft recently announced in their ridiculously wordy way that Windows Aero is dead. I really liked Aero and have a bit of a history with it. Window Clippings, the screen capture tool I originally created, was to the best of my knowledge the first to be able to perfectly capture the effect in a 32-bit alpha-blended image. I wrote extensively about the Desktop Window Manager that gave life to the translucent glass (this, this and this comes to mind).
Few apps that I know of ever took advantage of it, the most obvious examples being Internet Explorer 9 and Office 2010. There was the odd contribution from third parties, such as Google’s cute Chrome browser. Ironically, as I write this Chrome is on version 19 (nineteen!?) and they have still not been able to fix a glaring bug in their “chrome”. I must be the only one who notices such things.
I understand that Aero is not particularly power efficient compared to the new Metro UI and I get that it was not particularly easy to use unless your app was entirely written in Direct2D or Direct3D. Still it is sad to see it go. So long old friend.


