Talking with Microsoft’s Rey Bango on Open Web standards and testing IE. ![]()
I’m incredibly proud to say that I’ve published my second Pluralsight course,
Windows 8 Application Development With XAML and C# From Design to Delivery.
This course follows the design and development of a real project: Conference Buddy, that I’ve been developing for Telerik along with my good friends and co-workers Phil Japikse, Michael Crump, Jeff Fritz and Carey Payette.
Talking with Phil Haack and Jon Galloway about Git, GitHub, GitHub for Windows,
organizational structure and much more.
Today’s Windows Developer faces a crucial decision: whether to build for the new (shiny!) Windows 8 Store or to build for the Desktop. There are significant advantages to each, and they are, more or less, mutually exclusive.
Shameless self-promotion warning!
I have released my first (but not last) Pluralsight course, Windows 8 From Start To Store
. This XAML and C# – based course covers everything from design fundamentals to data to getting your app in the store.
In a previous blog post, I showed the repository pattern with local or remote data storage. In this blog post, based in part on work done for my upcoming book Pro Windows 8 With C# and XAML by Jesse Liberty and Jon Galloway, we’re going to explore storing data using Sqlite.
Yesterday, we looked at being a sharing source. This was surprisingly easy. Being a target would be more complex except that Visual Studio provides a template that greatly simplifies the process.
Everybody loves to share. (At least after they are beaten into doing so in pre-school.)
The ability to share from one application to another can be anything from useful to critical. Historically, we’ve seen a number of ways of doing this, the most enduring of which is the clipboard. Windows 8, however, introduces a system-wide sharing mechanism that is like the clipboard on steroids, and more important, which is easy to program and easy to use.
In a previous post, I showed a bit about how to implement the Search contract. Once you understand the changes to Package.appxmanifest and App.xaml.cs, however, you can save yourself the bother of mucking about with these, and let the template that comes with Visual Studio fix up all the plumbing for you.
In a previous post, I explained how to store data to a “known location” such as the My Documents folder. Often,
however, you will want to store local data to a subfolder of AppData on the user’s disk. This is even easier to do, because you need no special permissions or settings to access either local or roaming data files.
In this blog post, based in part on work done for my upcoming book Pro Windows 8 With C# and XAML by Jesse Liberty and Jon Galloway, we’re going to explore storing local data, but doing so in an extensible, reusable, well-factored way. In a later posting, I’ll use the same structure to store data using Sqlite.