Showing posts with label WinRT. Show all posts
Showing posts with label WinRT. Show all posts

Thursday, January 08, 2015

Coding4Fun Toolkit Lives! v2.0.9 released with more WinRT/WP 8.1 support

Invoke IT Limited - Coding4Fun v2.0.9 released #wpdev #windev #winrt

Coding4Fun toolkit v2.0.9 for Windows Platform dev has been released and packages are available for download from Nuget.

This update builds additional support for Windows Runtime on Windows Phone 8.1 and Windows 8.1. Controls added to this release include

  • MetroFlow control (Windows 8.1 and WP 8.1)
  • Prompts (Toast, User, Message, Input, PasswordInput) for WP 8.1
  • BrushToBrushConverter now allows use of parameter to set output Opacity.


SubramanyamRaju Windows Phone Tutorials(C# - XAML) - Great News! Coding4Fun Toolkit Controls are supported for Windows Phone 8.1- Part 1 (C#-Xaml)


Yesterday i found from twitter as 'Coding4Fun Toolkit is Supported for Windows Phone 8.1'.And i want to be say thanks to Hermit Dave for sharing this info on twitter. Now Coding4Fun toolkit v2.0.9 for Windows Platform dev has been released and packages are available for download from Nuget.
In WindowsPhone 8.0 we got lot of additional controls from Coding4Fun,The Coding4Fun Toolkit has multiple controls and useful items for XAML based applications.And current version v2.0.9  includes following controls.
  • MetroFlow control (Windows 8.1 and WP 8.1)
  • Prompts (Toast, User, Message, Input,About, PasswordInput) for WP 8.1
  • BrushToBrushConverter now allows use of parameter to set output Opacity.
Note: In Version 2.0.8,support was added for windowsphone store 8.1 and now more controls were ported across in 2.0.9. So that 2.0.9 is second version for wp8.1 store :)
...This article will teach you about 'How to use MessagePrompt control in WindowsPhone store 8.1 ?'.



Coding4Fun Toolkit



I thought I was seeing things when I started seeing activity on the Coding4Fun Toolkit project. Nope, it's alive and still kicking... Okay, so it wasn't a huge release, but still it's STILL a release! Kudo's to the new team and their work...


Related Past Post XRef:
Coding4Fun Toolkit v2 Released (fka Coding4Fun.Phone.Toolkit), now with Windows Store, Windows Phone 8 and Windows Phone 7!

Coding4Fun.Phone.Toolkit v1.5.0 Now Available...

Coding4Fun Windows Phone Toolkit (CF4 Blog Post)

Coding4Fun.Phone.Toolkit v1.3 Released (New Message Prompt, Password Prompt controls and Toast fixes + now NuGet'able too)
The Coding4Fun team has done it again, released another “Kit” that is… The Coding4Fun Windows Phone Toolkit
CF4DevKit (Coding 4 Fun Development Kit) 1.0 Released
Cool Coding with VS2008 and Vista via the Coding4Fun Developer Kit 2008 Vol 1 (Beta

Friday, April 25, 2014

Building Brokered LOB WinRT App's, a quick guide and a few tips to help you keep your hair...

Diederik Krols - Building Enterprise apps using Brokered Windows Runtime Components

This article shows step by step how to connect a side-loaded modern app to a legacy component via the “Brokered Windows Runtime Components for Side-Loaded applications” feature. This feature comes with Windows 8.1 Update and allows Modern apps to break outside the AppContainer and connect to desktop components such as legacy .NET class libraries. This gives the side-loaded app direct access to native platform capabilities, including COM Interop and P/Invoke. For a detailed introduction I would encourage you to take a look at this Build 2014 session by @devhawk and read this MSDN white paper. A Brokered Windows Runtime Component is a new type of component that bridges the technology gap between the Windows Runtime and the .NET world. It allows you to write a touch optimized modern Store app against legacy components that sit on the same desktop. As an example I created a legacy application with a data access layer DLL that uses SQL Server Express and Linq-to-SQL, and a Windows forms executable:


I tried for a couple of hours to build and link the necessary components the manual way, as explained in the White Paper. But I’m not really skilled in building Runtime Components, and the last time I saw the internals of a C++ project was a very long time ago in a galaxy far away. When I was about to give up, the Brokered WinRT Component Project Templates for Visual Studio were released. And this is what happened then:



The side-loaded app can not directly talk to the Brokered Component since it’s targeting a different framework family. The following happens when you try this out:


There needs to be a so called Brokered ProxySub in between the Modern app and the Brokered Windows Runtime Component. Fortunately there is a template for this:


If you run the app now, it still goes wrong:


You have to make sure that ...


Brokered Windows Runtime Components will enable the development of a new breed of corporate line-of-business apps: touch-first modern apps that are connected to existing enterprise data and processes.

Here’s the sample app, it was written with Visual Studio 2013 Update 2 (RC) for Windows 8.1 Update. If you want to play with it, don’t forget to run as Adminstrator and change the path in the app’s manifest:


As I've whined before (um... yesterday I think), there still needs to be allot done to help make Modern App's truly viable in the LOB world, but this is still one good step toward making a Modern LOB app workable. No one really wants to HAVE to rewrite our entire LOB stack (okay, we, dev's, usually want to rewrite it, but not to have to... ;). Re-use is good and this will help us do that. Now to see how it fares in the real world.


Related Past Post XRef:
LOB help in the WinRT world - "Brokered WinRT Component Project Templates"

Thursday, April 24, 2014

LOB help in the WinRT world - "Brokered WinRT Component Project Templates"

Brokered WinRT Components was one of the hits of Build 2014. These project templates will help you make your own...

Visual Studio Gallery - Brokered WinRT Component Project Templates

This package contains project templates used to created Brokered Windows Runtime Components and their Proxy Stubs, which enables side-loaded modern applications to communicate with pre-existing desktop components.

This solution works on Windows 8.1 update or later version.

It contains two project templates:

1. A C# project template for you to create the Desktop Windows Runtime components that are used to bridge modern application and pre-existing desktop code.

2. A C++ project template to generate the IPC proxy stub that will be used in your modern application.

For more details about the Brokered Windows Runtime Component, please review whitepaper on MSDN:

Here is a brief guidance on how to use the template to create a brokered WinRT component:

  1. Create a new Brokered WinRT Component using the Templates -> Visual C# -> Brokered Windows Runtime Component (Let’s call this BrokeredComponent)

  2. Make updates to Class.cs (change file name if needed) to define the component.



Brokered Windows Runtime Components for side-loaded Windows Store apps

[This documentation is preliminary and is subject to change.]

This paper discusses an enterprise-targeted feature for the Windows 8.1 Update that allows touch-friendly apps to use the existing code responsible for key business-critical operations.


Windows 8 and Windows 8.1 brings an entirely new class of applications, designed for touch, running on a new generation of hardware optimized for touch, and using a new runtime and APIs. The new runtime, called the Windows Runtime, brings with it a host of new functionality, new APIs for existing concepts and new generations of UI frameworks (XAML and HTML) for these applications.


The sample code that accompanies this paper may be downloaded from this location.

The new generation of applications have been designed to be distributed through the Windows Store and its related infrastructure. A new certifications process for these applications include requirements that deprecate a large number of older APIs and frameworks. While creating a vastly simpler programming surface for the new style and design requirements, many existing enterprise software assets have been left in a state of limbo. They continue to operate in their "desktop" world, but are difficult to leverage in the new touch-friendly applications. Calling these deprecated APIs or using the legacy frameworks causes issues to be raised in the WACK certification tool included in Visual Studio and run as part of Windows Store submission.

Recognizing that critical business functions and rules are embodied in existing software assets and that enterprises have a wide variety of scenarios for which the new application style will be highly productive, the Windows 8.1 Update includes a new feature called Brokered Windows Runtime Components for side-loaded applications. We use the term IPC (inter-process communication) to describe the ability to run existing desktop software assets in one process (desktop component) while interacting with this code in a Windows Store app. This is a familiar model to enterprise developers as data base applications and applications utilizing NT Services in Windows share a similar multi-process architecture.

Side-loading of the application is a critical component of this feature. Enterprise-specific applications have no place in the general consumer Windows Store and corporations have very specific requirements around security, privacy, distribution, setup, and servicing. As such, the side-loading model is both a requirement of those who would use this feature and a critical implementation detail.

Data-centric applications are a key target for this application architecture. It is envisioned that existing business rules ensconced, for example, in SQL Server, will be a common part of the desktop component. This is certainly not the only type of functionality that can be proffered by the desktop component, but a large part of the demand for this feature is related to existing data and business logic.

Lastly, given the overwhelming penetration of the .NET runtime and the C# language in enterprise development, this feature was developed with an emphasis on using .NET 4.5 for both the Windows Store app and the desktop component sides. While there are other languages and runtimes possible for the Windows Store app, the accompanying sample only illustrates C#, and the desktop component portion is restricted to the .NET runtime exclusively.


Personally I still think there's more required, much better distribution story, like  an inside-the-firewall app store, but this IS a good step forward and will help smooth the LOB Modern App way a bit...

Tuesday, December 17, 2013

Surface RT/Pro/Pro 2 User Guide PDF's available

Kurt Shintaku's Blog - DOWNLOAD: Surface RT/Pro/Pro 2 User Guides

If you’re new to Surface, download your Surface User Guide. These printable manuals have info and tips to help you get the most from your Surface.

Taken from: [GD: Post Leached in Full]


Will come in handy for those who get a Surface under the Christmas Tree...

Monday, December 09, 2013

Kudos to Kodu's Windows Store Release

Windows - Kodu



Kodu lets you create games through a simple visual programming language. Kodu can be used to teach creativity, problem solving, storytelling, as well as programming. Anyone can use Kodu to make a game with no design or programming skills.


  • Kodu is a rich tool for narrative creation and storytelling
  • Kodu demonstrates that programming is a creative medium
  • Kodu helps children with critical thinking, breaking a complex goal into manageable steps, and iterate on the design process
  • Kodu introduces the logic and problem solving of programming
  • Kodu introduces conditions and sequences, which teaches cause and effect
  • Kodu can be taught by any teacher, no previous programming expertise required
  • Students learn about cooperation, logic and creativity in addition to programming



English (United States) and 1 other languages


Show all languages

Supported processors

x86, x64, ARM

Kodu Game Lab


More Kodu, just in time for the holidays and on all our favorite Windows tablets and touch devices... :)

(Microsoft News - Microsoft Releases Kodu Game Development Tool For Free In Windows Store)


Related Past Post XRef:
Kodu Game Lab v1.4.1.0
Are you an Educator/Teacher? Microsoft has free software just for you!
Kodu, the Microsoft Research visual game programming language targeted at beginning programmers, now available for PC’s (Tech Preview)

Monday, November 25, 2013

If you're not cheating, you're not... using these new Windows Runtime Network API cheat sheets

Windows App Builder Blog - Network API cheat sheets available now in the download center

The network APIs have tremendous depth and enable your app to work in many ways.  But it can be hard to figure out how and when to use the different APIs.  To help you out, the Windows Networking Team has created poster-sized cheat sheets with overviews and code samples of the most popular network APIs.  And, we’re working on more!

The cheat sheets tell you about the different APIs. But which API is the right one to use, and when? Here's an easy way to figure it out:

  • Are you connecting to an HTTP server?
  • Are you connected to a classic TCP or UDP server?  Or to Bluetooth? Use the Windows.Networking.StreamSocket (TCP and Bluetooth) or DatagramSocket (UDP and Multicast) classes.
  • Are you connecting to one of the new "WebSocket" servers?  They aren't classic sockets (and don't interoperate with classic sockets), but they can tunnel through corporate proxies and interoperate with up-to-date HTML5 browsers.  Websockets are in the Windows.Networking.Sockets namespace.
  • Are you connecting to people in the same room? (For example, with Near Field Communication (NFC) tap to connect)?  If so, use the Windows.Networking.Proximity PeerFinder and related classes; this can give you back a StreamSocket that you can use to communicate with peers.

Our first pack of cheat sheets are for the HttpClient, Sockets, and Background Transfer APIs.  Download the pack now from the Microsoft Download Center. And let us know what other cheat sheets you need! [GD: Post Leach Level: 99%]

Microsoft Downloads - HttpClient. Background Transfer, and Sockets Network API Poster for Windows Runtime Developers

Windows runtime developers! This Network API poster describes some of the most popular Network APIs in the Windows Runtime classes. The set of posters includes HttpClient, Background Transfer, and Sockets 

Version: 8.1

Date Published: 11/13/2013

WinRT81-HttpClient-BT-Socket-Poster.pdf, 502 KB

The poster is provided in PDF format. When you print it from the PDF, specify the dimensions as landscape Tabloid size (11 inches by 17 inches).



Worse case, this will make for nice Cube Poster-ware... Best case it will help you build even more awesome .Net'enabled Windows Runtime app's... :)

Thursday, October 03, 2013

XAML Spy v2 Beta Visual Studio now available... (think "Spy++ for XAML as a VS Extension")

XAML Spy - XAML Spy for Visual Studio [beta]

First Floor Software is proud to announce the immediate availability of the first beta release of XAML Spy for Visual Studio. XAML Spy for Visual Studio enables spying on Silverlight, Windows Phone, Windows Store and WPF apps right in Visual Studio.

XAML Spy for Visual Studio is a VS2012 and 2013 extension for XAML projects. The extension is part of XAML Spy 2. You are only three steps away from happiness:

  1. Download and install XAML Spy 2 (beta). Start Visual Studio and load your XAML project.
  2. Right-mouse click your XAML project, select Enable XAML Spy, compile and run your app in DEBUG mode.
  3. Switch back to Visual Studio, open the XAML Spy Explorer (View > Other Windows > XAML Spy Explorer) and start inspecting your app.

Tip: hit Alt-Enter to open the Visual Studio property grid for details on the selected object in the XAML Spy Explorer.


XAML Spy for Visual Studio adds a XAML Spy Explorer tool window to Visual Studio 2012 and 2013. The XAML Spy Explorer provides a real-time view of your running XAML app, with access to the app's package, isolated storage, user interface, and more.



XAML Spy 2

XAML Spy for Visual Studio is part of the next major release of XAML Spy (version 2). At this point in time, version 2 only consists of the Visual Studio extension. The standalone XAML Spy app (with its Modern UI interface) will be added in a future update. This beta release replaces any XAML Spy version 1 you may have installed. If your environment doesn't meet the requirements for XAML Spy for Visual Studio, or if you require features not available yet in this beta release, do not install this beta release. Learn more about the requirements and features in the next paragraphs.

XAML Spy for Visual Studio requires at least the Professional Edition of Visual Studio 2012 or 2013. The Express editions of Visual Studio are not supported.



Feel free to install and use this public beta to spy on your XAML apps. The release is fully functional, and does not require a license. This version will cease to function on October 15, 2013. Your feedback is highly appreciated, be sure to send us your comments and questions. XAML Spy 2 is available in the download section.

While the beta is only free for a couple days yet, that still a few days where you can play with it and check it out...

Friday, May 24, 2013

Windows 8.1 Pre-beta WinRT API Spelunking (Think, "What's new in the Win8.1 WinRT API's" or "Wow, this is a ton of information..." or "OMG, Justin needs a life..." ;)

Justin Angel - Pre-beta Windows 8.1 WinRT Developer APIs

In this article we’ll review new developer WinRT features that’ll be released in the upcoming Windows 8 release (dubbed “Windows 8.1” / “Windows Blue”). Microsoft recently announced that during June 2013’s BUILD conference a developer preview of Windows 8.1 will be released for download. In the meanwhile many Windows 8.1 “leaked” images are available online. These “leaked” images allows us to get a sneak preview of the featuresets that’ll be announced in BUILD conference. For the length of this article we’ll go over those features.

Methodology: How was this research done?

Windows 8.1 images contain WinMD files describing their embedded Windows 8.1 developers APIs. It’s possible to get to Win8.1’s WinMD files and then compare them to the existing Windows 8 RTM WinMD files. This entire article is based upon using Reflection to see those API differences.

  1. Download the latest Windows 8.1 “leaked” image. This article was based on an image named “9385.0.FBL_PARTNER_OUT17.130415-2049_X86FRE_CLIENT_EN-US-PL-PL-RU-RU.ISO”.
  2. Create a bootable USB drive from the ISO file and Install it on a nearby machine.
  3. Win8.1’s WinMD files can be found under the following directory: C:\Windows\System32\WinMetadata
  4. Using Microsoft’s Framework Design Studio it’s then possible to compare the WinMD files from a WIndows 8.1 “leaked” image and Windows 8 RTM. 



Table of Contents

  1. Bluetooth 4.0 RfComm and GATT support
  2. Point of sale: Barcode scanners and Magnetic card readers
  3. Smart Cards
  4. Lock screen Image Apps
  5. VPN support for Metro apps
  6. Scanner APIs and apps
  7. Support for any External / USB device
  8. Native PDF rendering in apps
  9. Multiple screens projection support in apps
  10. XAML/WinJS: New resolution scaling support / Super-high resolution tablets
  11. Camera: Low-lag cameras / HDR
  12. New Metro App Types: Appointments, LockScreen, Contacts and GeoLoc
  13. New App Type: GeoFenced activation
  14. New App Type: Lock screen call
  15. New App Type: Appointments Provider
  16. Text-to-speech
  17. Read-write access to Camera roll, Saved pictures and playlists
  18. XAML/WinJS: new SearchBox control
  19. XAML/WinJS: Hubs for SemanticZoom
  20. XAML: DatePicker and TimePicker
  21. XAML: Flyout, MenuFlyout and SettingsMenuFlyout
  22. XAML: AppBar simplification
  23. XAML: DataBinding Improvements
  24. Globalization: Currencies, Numeral systems and Numerical formatters
  25. Other minor but important Win8.1 features
  26. How to code Win8.1 C# apps before public beta?
  27. How to develop Win8.1 WinJS apps before public beta?
  28. Disclaimer: Please don’t sue me


This is a book length, "omg, this looks like a ton of work" look at the unreleased Windows 8.1 WinRT changes


(via Windows Enterprise Desktop - Analysis of Windows 8.1 “Blue” APIs Reveals Cool Coming Attractions)

Thursday, April 25, 2013

Infragistics Releases 13.1 with new set of Windows Metro/Modern/UI XAML/HTML controls (which is now in the box for NetAdvantage Ultimate & NetAdvantage .Net subscribers)

Infragistics Releases 13.1

The wait is over! This morning, Infragistics released NetAdvantage Ultimate 13.1 and our related 13.1 toolsets and products to the community. Ultimate 13.1 is the only design and development toolset on the market that lets you create both hybrid and native mobile applications, in addition to modern and touch-friendly apps for the desktop and web. The release includes updated versions of our WPF, Silverlight, iOS (NucliOS), ASP.NET, and HTML5/jQuery (Ignite UI) toolsets, as well as brand new to market Windows UI controls. Ultimate also features the new Indigo Studio design tool which lets you create rapid, interactive prototypes of your application UIs while maintaining your focus on your users, and whole lot more. 

Highlights in this release of Infragistics NetAdvantage platform include:

  • New toolset NetAdvantage for Windows UI offering 20 XAML and HTML controls for native Windows 8 app development.
  • ...


Brian Lagunas - Introducing NetAdvantage for Windows UI–Your Path to Windows 8

Your wait is over!  NetAdvantage for Windows UI is HERE!  Since the announcement of Windows 8 at the Microsoft //BUILD/ event in Anaheim, CA back in 2011, Infragistics has been watching the market trends, listening to customers, and working closely with Microsoft to create the best Windows 8 control toolset available.  No matter what your UI preference, we have leveraged our existing codebase to create a familiar and unified development experience for both XAML and HTML.

Whether you are a line of business developer writing internal applications, or a developer writing consumer based applications that will be published in the Windows Store; NetAdvantage for Windows UI provides the tools you need to create fast and fluid, rich, touch enabled, true Windows 8 experiences.  Now is the time to choose your path to Windows 8!


If you are a XAML developer, then our XAML based Windows UI controls are for you.  Our WinUI XAML controls are based off our ever popular NetAdvantage for WPF and Silverlight, so if you currently use our XAML controls, then moving into developing for Windows 8 just got a lot easier.  With the same feature set, same API, and same great controls, you can take the knowledge and experience you already have and start writing touch enabled Windows Store applications without skipping a beat.

I bet you’re wondering what you get for the XAML stack.  Well, let’s check out the controls.

  • Data Chart
  • Grid – CTP
  • Barcode
  • Calendar
  • Currency Input
  • DateTime Input
  • Masked Input
  • Numeric Input
  • Excel Framework – CTP
  • Persistence Framework – CTP

Wow, that’s a lot of XAML!  Let’s check these controls out in a little more detail.



What’s that you say?  You’re not a XAML developer?  You come from the world of HTML and jQuery?  Give you a DIV and a CSS style any day?  Well, okay I will!  Our NetAdvantage for Windows UI also ships with some great butt-kicking HTML controls.  If you currently use our IgniteUI product, that’s our HTML and jQuery controls, then you’re going to love this.  Our WinUI HTML controls are based off our IgniteUI controls.  Don’t use our IgniteUI controls?  No problem, f you know HTML and jQuery then you already know how to use our controls.  Either way, you are ready to start writing stunning, finger burning, touch enabled HTML Windows Store applications with our HTML based WINUI controls.

So what did we give you in our first release of WinUI HTML?  Let’s take a looksy…

  • Grid
  • Hierarchical Grid
  • Data Chart
  • Map
  • Pie Chart
  • Date Picker
  • Date Editor
  • Currency Editor
  • Numeric Editor
  • Masked Editor
  • Text Editor

Say Whhhaaaaatttt!  Yeah, that’s a ton of great HTML controls.  Everything you need to get started writing your app.  Let’s dig a little deeper into these babies!


There's nothing like getting something new in a package/subscription you're already paying for. If you're a Infragistics NetAdvantage Ultimate & NetAdvantage .Net subscriber, there's not one new control suite to play with but two! (but both for Win8 Modern UI/WinStore apps). (There's also a free 30 day trial)

Good to see a top tier vendor make an investment in Windows 8 WinStore Apps.

Also it's pretty cool how they leveraged their existing control suite to provide the XAML/HTML controls. A huge plus if you are using their existing controls.

Want to play with the controls now, free? There are two WinStore app's for that... and


Related Past Post XRef:
Prism? Infragistics? Dock and Ribbon? Oh my...
Ignite your web dev with the Infragistics Ignite UI learning series by Craig Shoemaker
Navigation, MVVM, XAML and a little IG (Infragistics) in this "Building IG Outlook" video
Infragistics gives their Windows Forms controls some Coded UI Testing love
Parsing 101 with the Infragistics Parsing Framework
Don't be blue, be Indigo! Indigo Studio from Infragistics released today (and it's free forever too)
Infragistics shows off their new Undo/Redo Framework CTP
Infragistics Blogs
Problem/Solution with the Infragistics NetAdvantage 2005 Vol 3 CLR2 Toolbox Install Utility ("Tools.InstallCommunityControls" is not valid)
Upgrading an Existing Application to use the New Infragistics Application Styling Feature
Infragistics NetAdvantage 2006 Volume 1 Released...
Infragistics NetAdvantage Select 2008 Volume 3 released today
New Infragistics ClickOnce & WinGrid KB Articles
Infragistics - Installing NetAdvantage for .NET on Windows Vista

Friday, April 19, 2013

Bye bye Kona code name... Hello "Prism for Windows Runtime"

Brian Noyes Blog - Kona is Dead, Long Live Prism!

If you have read my blog, seen me speak at conferences or user groups, or read some of my articles lately you might know I have been working with the Microsoft patterns & practices team on guidance for Windows Store Business apps. This guidance has been code named “Kona” up until recently, and I’ve posted and written articles on that in various places.

As the team was getting the guidance ready for release, they decided to rename it to “Prism for Windows Runtime”. The names have not all been updated on the Codeplex site or in the downloads yet, but the code has been refactored to the final namespaces and project names that it will ship with.

Specifically the guidance is called “Prism for Windows Runtime”, and it is guidance on building loosely coupled, maintainable, testable applications based on the MVVM pattern for WinRT, especially Line of Business or Business to Consumer applications.

The guidance contains:


If you want to learn more, be sure to check out my article series here, and keep an eye out for my Pluralsight Course that will be out in a month or so titled “Building Windows Store Business apps with Prism”.


Prism for Windows RT (fka Kona) - Prism for Windows Store apps Drop April 10, 2013


I'm happy about this name change... And glad to see Prism, even in a Windows Runtime world, continue to get some attention. Also, as Brian notes, the "Kona" code name is still there on the project. These things can take a bit to change


Related Past Post XRef:
Windows 8 + Kona + Steve = Itinerary Hunter
Kona, Kona, Kona! [Think P&P dev guidance for composite application WinStore Apps {Yes, like Prism, but not}]

Friday, February 08, 2013

One download of wonderful [Samples] for Windows 8. 258 samples, one'ish download. C++, C#, JavaScript and VB samples all available

Windows Dev Center - Windows 8 app samples




This sample pack includes all the app code examples developed for Windows 8. The sample pack provides a convenient way to download all the samples at once. The samples in this sample pack are available in C#, C++, VB.NET, and JavaScript.

The Windows Samples Gallery contains a variety of code samples that exercise the various new programming models, platforms, features, and components available in Windows 8 and/or Windows Server 2012. These downloadable samples are provided as compressed ZIP files that contain a Visual Studio solution (SLN) file for the sample, along with the source files, assets, resources, and metadata necessary to successfully compile and run the sample. For more information about the programming models, platforms, languages, and APIs demonstrated in this sample, please refer to the guidance, tutorials, and reference topics provided in the Windows 8 documentation available in the Windows Developer Center. This sample is provided as-is in order to indicate or demonstrate the functionality of the programming models and feature APIs for Windows 8 and/or Windows Server 2012. Please provide feedback on this sample!

I swear I thought I blogged about this, but I can't find it (and if I can't Bing it, it doesn't exist... right? :/ ) Anyway, better late and all that. There should be enough samples here to keep you busy this weekend or so...

(via Microsoft Pakistan Community Blog - 200 Windows 8 Sample App Pack)


Related Past Post XRef:
Metro XAML and HTML Control Sample Packs (Two downloads, bunches of controls sampled, lots of code examples, hours of...)

Monday, February 04, 2013

Coding4Fun Toolkit v2 Released (fka Coding4Fun.Phone.Toolkit), now with Windows Store, Windows Phone 8 and Windows Phone 7!

Coding4Fun Tools - Coding4Fun Toolkit v2.0.0

New Stuff

  • Shared code base between Windows Store, Windows Phone 7, and Windows 8
  • Shared XAML base between Windows Store, Windows Phone 7, and Windows 8
  • AppBarPrompt for WP7 and WP8
  • Polishing on prompts
  • SolidColorBrushToColorConverter
  • ImageTile now has a Label
  • TiltEffect is now included
  • GzipWebClient
  • InputPrompt / PasswordInputPrompt - TextWrapping now supported
  • TimeSpanPicker is now in the Control assembly.

Breaking Changes
  • Namespace change to Coding4Fun.Toolkit from Coding4Fun.Phone
    • This was due to supporting Windows Store
  • RoundToggleButton, RoundButton, OpacityToggleButton, Tile, and ImageTile content property shifted to Label property. Context is for the main body of the button instead of the bottom label.

Bug Fixes
  • A lot ... will attempt to list them all
  • ...

WHAT? You've not heard of this toolkit? Well...

Coding4Fun Tools 

This is where Coding4Fun will house all our cool controls and tools that we come up with!  If there is a bug [report], a needed control/feature that could benefit everyone [chat], or you want to help out [email], please reach out to us!




That last snap is the best part of this project and shows how this is a true community effort.


Related Past Post XRef:
Coding4Fun.Phone.Toolkit v1.5.0 Now Available...

Coding4Fun Windows Phone Toolkit (CF4 Blog Post)

Coding4Fun.Phone.Toolkit v1.3 Released (New Message Prompt, Password Prompt controls and Toast fixes + now NuGet'able too)
The Coding4Fun team has done it again, released another “Kit” that is… The Coding4Fun Windows Phone Toolkit
CF4DevKit (Coding 4 Fun Development Kit) 1.0 Released
Cool Coding with VS2008 and Vista via the Coding4Fun Developer Kit 2008 Vol 1 (Beta

Friday, January 25, 2013

Windows 8 Drone... as in "AR.Drone 2.0 API for Windows Store Apps"

Try, Catch, Finally... - AR.Drone 2.0 API for Windows Store Apps

Source Code:

Difficulty: Beginner
Cost: $299.95 for the AR.Drone 2.0
Software Needed: Visual Studio

The AR.Drone 2.0

The Parrot AR.Drone 2.0 is an awesome device packed with cool features. The drone contains two cameras, one pointed forward that streams live video, and one pointed downwards (for all your surveillance needs). Its got four powerful engines that make it fast and maneuverable. The drone’s firmware keeps it stable and level while stationary or performing maneuvers, handling a huge burden for the user. It’s a fun device to write code for, and even more fun to pilot when you’re done!

There’s a few projects that have created AR.Drone APIs that can be used for Windows 8 Desktop Apps. However, I wanted to fly my drone from a Windows Store App, so I decided to build my own API compatible with WinRT. The result is covered in this series of posts. Thanks to Nisha Singh ( and everyone else who helped me out with this project!

In the first post, I’ll go over how the API handles communicating with and controlling the drone, and then demonstrate how to use the API to make a simple control App.


I sooooo want this. How cool would it be to create a touch, gesture and movement based Surface app to control a Drone? Add in a Sharing contract to share what your drone just saw and where... Oh and... Wow, what about... [Must control self... Put away wallet. Must not buy a drone... must... buy... drone.. MUST... ]   :P

Tuesday, January 22, 2013

You are Here... "Bing Maps for Windows Store Apps Training Kit"

Bing Maps Blog - Bing Maps for Windows Store Apps Training Kit

Bing Maps for Windows Store apps combine the power of Windows 8 and Bing Maps to provide an enhanced mapping experience for Windows Store apps. Developers can use this Bing Maps control to incorporate the latest road maps, aerial views, and low-angle high-resolution images into a Windows Store app.

Today we are happy to announce the release of the Bing Maps for Windows Store Apps Training Kit. This training kit is made up of a PowerPoint slide deck which serves as an overview to create a Windows Store App using Bing Maps. The slide deck also includes information on existing applications which use Bing Maps that are in the Windows Store. In addition to the training deck there are 2 labs. The first has been designed for the JavaScript developer and the second, for the Native code developer. Each lab is made up of multiple exercises and should take around 90 minutes to complete.


I'm just a sucker for Training Kits...

Thursday, January 10, 2013

Windows Store App's and Databases (the series)

Windows Store apps development support - Using database in Windows Store apps (I)


There are lots of discussions about using database in Windows Store apps in MSDN forum. These discussions mainly focus on the usage of SQL database. Based on this scenario, we developed a series of articles along with sample code and demos used to demonstrate how to access both local database and remote database.

This topic consists of four categories as below.

  1. Overview of main approaches to access database in Windows Store apps.
  2. How to access local database:
    1. How to use SQLite for Windows Runtime and how to use sqlite-net library to manipulate SQLite database.
    2. How to use Extensible Storage Engine (ESE) or known as JET APIs.
  3. How to use WCF to access database in Windows Store apps.
  4. How to access remote database.

First, we talk about how to access local database in Windows Store apps. SQLite would be a good choice.


I find it hard to envision an app that doesn't have some kind of data store. Oh sure, I can see simple app's, but anything that does anything over time or "remembers" something, has any kind of state has to store it somewhere. And when building Windows Store app's in this version of Windows, database access is a little v1'ish. So until it gets better (assuming it does?) this kind of information is going to be important to have (and keep for future reference).

50! As in 50 "store ready" Windows 8 application templates (in both C#/XAML & HTML/JS)....(and free!)

MSDN Malaysia - Windows 8 Design Templates is now ready for all the developers

Good news to all the developers!! There are 50 “Store Ready” templates for Windows 8 in the form of Visual Studio projects. Templates are a great way to get started. Developers can now choose a design template which is closest to their design/implementation, customize and give life to their idea. The templates have been created keeping in mind the Windows 8 style & experience.  Just by binding the relevant data, developers should have a good looking app that runs in the paradigm of Windows 8.


image - Build






Templates! Now that's a bunch of templates... All told, 450MB of compressed templates. And in both C#/XAML and HTML/JS.

Man, if this is enough starter kits/templates to get you started...

(via Windows Phone Geek - 50 FREE Windows 8 Design Templates for developers)

Wednesday, January 09, 2013

Oh TFS... OData Service for TFS v2 beta released (with a companion Windows 8 app too)

Brian Keller - OData Service for Team Foundation Server v2

Today we are releasing the beta of the OData Service for Team Foundation Server v2 along with a sample Windows Store application

The purpose of this service is to help developers work with data from Team Foundation Server on multiple device types (such as smartphones and tablets) and operating systems. OData provides a great solution for this goal, and has been embraced by numerous developers for building great device-specific applications. OData is accessible from any device and application stack which supports HTTP requests.

The OData service interacts directly with the TFS client object model, and will work with CodePlex, Team Foundation Server 2010 and Team Foundation Server 2012.

TFS Dashboard for Windows Store
My colleague Nisha Singh built a Windows Store application – TFS Dashboard – using this OData Service. All of the source code is available for the application which can be downloaded alongside the OData Service. This is a sample which you can extend and customize yourself to learn more about how to consume the OData Service in your own applications. Nisha has more information about this application on her blog where she will be sharing additional information soon about how she implemented the Live tiles, Search and Share features supported by WinRT APIs.



I should make it clear that this is not an official release from the TFS engineering team. The TFS engineering team has reviewed the service and approved of the approach we are taking, but there is no official support for this service. That said, all of the source code is provided for you, the license permits you to use it in production and extend it for your own purposes, and we are interested in (but not committed to) continuing to add capabilities over time.

Will this work with Team Foundation Service?
Not currently, although we are very excited about this possibility in the future. We are working on a release which work with Team Foundation Service but I do not have a timeline to share at the moment. More details will be posted as an update to this blog post when it is available.


Microsoft Downloads - OData Service for Team Foundation Server v2 Beta

This sample allows you to expose an OData service for Team Foundation Server (2010 and 2012). This service can make it easier to build applications for a multitude of devices which consume or manipulate data stored in Team Foundation Server.

Version: 2.0 Beta
Date published: 1/7/2013

Language: English

ODataForTFS.V2.Beta.exe, 25.3 MB

TFSDashboardBeta.exe, 1.4 MB

The purpose of this project is to help developers work with data from Team Foundation Server (2010 and 2012) on multiple device types (such as smartphones and tablets) and operating systems. OData provides a great solution for this goal, and has been embraced by numerous developers for building great device-specific applications. OData is accessible from any device and application stack which supports HTTP requests. This OData service interacts directly with the TFS client object model. To get information about the OData service, please visit Brian Keller's blog.

The download also includes a Windows 8 Store App sample. TFS Dashboard is a sample Windows 8 Store App that connects to Team Foundation Server. The TFS Dashboard App currently implements the Live tiles, Search and Share features supported by WinRT APIs. This App is primarily built to get users thinking towards building great Windows 8 App Store Apps, and to provide as an example for how to consume the OData Service for Team Foundation Server. Please visit Nisha Singh's blog for more information about the App.

Can't wait to see this go RTW (and have TFService support... )

Things on the OData front have been pretty quite, so it's good to see continued support and usage...


Related Past Post XRef:
OData Service for Team Foundation Server 2010 v1.0 RTW!
Opening TFS to the world via supported "web" API - OData For TFS (Beta) (Oh and you can use OData with CodePlex now too!)

Monday, January 07, 2013

Kona, Kona, Kona! [Think P&P dev guidance for composite application WinStore Apps {Yes, like Prism, but not}]

Infragistics - Introducing Kona Guidance for Windows 8 Application Development (Think of it as Prism for Windows 8, but not really)

I am extremely excited to announce a new project from the smart people at Microsoft’s Patterns & Practices team called Kona.  What is Kona you ask?  Kona is the new developer guidance for developing line of business applications for Windows 8.  Initially this project was called Prism for WinRT, but as it turns out, it’s really not Prism running on Windows 8, but rather a new set of guidance for developing Windows 8 applications.

Wait… just... a... minute Brian.  What do you mean it’s not “Prism” running on Windows 8?  What do you mean “new guidance”?  Well, if you download Kona and expect to start adding regions and modules like you’re used to, then you might get a bit frustrated looking for the attached properties and IModule interface.  Why?  Well, because it’s not there!  Actually there is a lot of Prism code that you are used to having that is not there and will not be there.  Why do you ask?  The answer is simple; it’s Windows 8.  Huh!?  It’s a new platform, and it has changed significantly compared to WPF and Silverlight.  When they were looking at doing the “port” of Prism, they soon realized that a lot of capabilities just didn’t make sense to bring over to the new platform.  Hence, a new set of guidance using a new set of APIs that are specific to the new Windows 8 platform.

Now not everything was ditched.  Some things, not a lot, made sense to bring over.  DelegateCommand and DelegateCommand<T> is still there.  Guidance on MVVM (Model-View-ViewModel) is still there, but honestly I don’t agree with the implementation.  Keep in mind, this is the first initial drop of Kona, so we can always make improvements to the code base.  Everything is a learning experience.






Interesting. Brian's post is much more complete that you'll find yet on the codeplex page,, but as he said, this is just the first drop... Will be watching for this now though... :)

Thursday, January 03, 2013

What Windows Runtime runs where?

Jim O'Neil - Technology Evangelist - Windows Runtime–what’s supported where?

As I’m sure you've heard, Windows Phone 8 and Windows Store (nee Metro) applications share a common core operating system, and that’s great news for developers looking to take advantage of both platforms with a single or complementary applications.

The common core does not, however, mean that the platforms are identical – in fact, only about 1/3 of the Windows Runtime API members are available on both platforms, and there are some APIs that are specific to either Windows Phone or Windows 8 due the unique experiences or features of the hardware.

Then, of course, there’s a .NET API available for both Windows Store applications and Windows Phone applications each a somewhat differing subset of the complete .NET API you’ve been using to build Windows Forms, WPF and ASP.NET applications for years.

As someone that’s been transitioning his skills from core .NET development to the Windows Runtime, I share the pain of trying to make that call to API X and finding it’s not supported on Windows 8 (or Windows Phone) or wondering why the namespace that I’ve used for years refused to resolve in a new Windows 8 app.

The good news is that the documentation is there, but there are some subtleties and nuances, so I’ve pulled this post together to outline some of the tricks and links I’ve discovered.




We've heard what Windows Runtime is available on a number of devices, but only pieces and parts are available in a given space... So what runs where? Jim's post helps us find what runs where for the Runtime. Worse case, it's a great resource link post... :)

Thursday, December 13, 2012

AppMock - Free Windows Store App to Design Windows Store App's

AppMock by Telerik



Telerik AppMock allows you to quickly and easily create prototypes of your Windows Store applications. Providing a rich set of Windows 8 Style tools and components, conveniently grouped in galleries and categories, you can simply drag and drop UI elements onto the design surface to arrange the layout and flow of your application. You can organize the prototypes in pages (called sheets) and projects and in the end you can run the projects to see all that in action, by navigating through the pages using preset links (hot-spots).


  • Create/Save/Open projects
  • Create pages/sheets
  • Drag and Drop shapes onto the design surface
  • Rich Galleries - Interactivity, Buttons&Links, Text&Input, Data Visualization, Media, Layout, Editors, Loading indicators, Data&Scheduling, Navigation, Gestures, Comments, Flow Charts, etc.
  • Customize the shapes - cut/copy/paste/resize/rotate/bring to front/set text/font-size/links/etc.
  • Undo/Redo
  • Multiple Selection of shapes
  • Navigate between pages/sheets
  • Run projects and use links between the pages/sheets
  • Search and Share via the charms
  • Pin projects to the start screen
  • Export projects

Telerik AppMock


Most Important Features/Behaviors

Creating Projects

Telerik AppMock allows you to organize your prototypes in projects by letting you:

  • Create new Project and give it a custom name
  • Save and Open the newly created Project
  • Rename your Project

Using the Design surface

Telerik AppMock supports two different modes – Design-time and Run-time. While you are designing (mocking) your application you are in the Design mode. It is visually split into a ToolBox (on the left, containing the Galleries) and Design surface on the right.


Creating Sheets (Pages)

Every project consists of sheets. A sheet represents a single screen of your application. You can:

  • Save (Save as) a sheet
  • Add/Remove sheet from the project
  • Copy/Paste the entire sheet

Using the rich Galleries

Telerik AppMock comes with a set of predefined galleries containing various UI shapes. Each shape represents a component or tool that can show certain logic of your app. For convenience all shapes are grouped in categories such as Navigation, Interactivity, etc. In addition there’s a search box right at the top of the toolbox (the panel containing all shapes) to enable you quickly find a tool or component. You can drag and drop any shape from the toolbox onto the design surface. Following is the list of predefined galleries:

  • Windows 8 Controls containing groups of shapes such as Interactivity, Buttons&Links, Text&Input, Data Visualization, Media, Layout, Editors, Loading indicators, Data&Scheduling, Navigation
  • Gestures
  • Comments
  • Basic Shapes - containing groups of shapes such as Flow Chart and Arrows


Now that's kind of cool... Love that there's an ARM version too (so should work on Surface :)

(via Dan Rigby - Windows Store Developer Links – 2012-12-13)