Moving existing Win 8.1 App to Win Phone 8.1 with new Universal App project – HypeMix has a go!

This a quick and dirty write up of how I moved my existing Windows 8.1 App to Windows Phone 8.1 in a weekend. Now before we get into that I’m going to be honest and say there is still some work to do around the UI, as playing music on the phone is slightly different to a PC or Tablet. What I’m talking about here is all the rest of the work.

So, I set out on my ambition goal with a simple step. My current solution had 4 Projects, one for the app, one for the API that it uses, one for tests and a second for tests just to be safe. If you want to play with the app you can get it here –

Step 1:

Right click on the Win 8.1 Project and Click “Add windows Phone project”

This gives you a “Shared” section, if you’ve worked with linked files before this is along those lines. When you compile each of the Win or WinPhone projects, the files in shared are included.

Step 2:


Now that you’ve got this lovely shared section you can move over all the obvious bits that you want to share. To kick this off I moved over my Commands, Exceptions, Services and ViewModels.

(To clarify the app uses Reactive Extensions to create a Publish and Subscribe architecture. When you click a button this binds to a Command on a ViewModel. The Command publishes an Event and these events are subscribed to by one or more services.

For example, Clicking “Play” invokes the “PlayPauseCommand” which in turn publishes a “PlayPause” Event. This event is subscribed to by the “MediaService”, when received the service starts playing the track. It’s also subscribed to by the “NotificationService” which pops up a toast to inform the user about which track is playing)

The first awesome thing I saw here was that my existing Win8.1 app still worked fine, moving the stuff to the shared section hadn’t had any effect on it. Big win, no changes needed to existing app so far!

The second awesome thing I saw here was EVERY BIT OF CODE, not counting the XAML and code behind ~8 files, was shared. That’s right, EVERY ONE OF THE 1.2K LINES OF CODE in the Windows 8.1 Solution could be shared. So far so good, let’s see how the API project gets on.

Step 3:

I mentioned earlier that I have a Windows 8.1 Class Library, which implements the HypeM Api. Now in the new SDK we have Universal App – Portable Class library. This is just a PCL which targets Win8.1 and WinPhone 8.1. So I can take advantage of this I needed to move all my stuff over to the new project type.

 let me know that you can simply retarget your project to Windows Phone 8.1 by going into properties and selecting Windows Phone. As this is a much simpler than using linked files I’ve cross out my original bit and moved to using this!



To do this I created a new “Universal App Portable Class Library”.

Then I used project linker to link all the files and add them into the new project type. (I had to download the VSIX file and alter the manifest so that it would work with VS2013 but once I’d done that it was all good, VSIX below)

After re-targeting the library I hit my first snag. When I happily hit F6, expecting the same level of success, my heart sunk as I saw errors. “Here we go” I thought, I’m going to have to refactor loads of code.

Once I’d talked myself back from the edge and actually looked at the errors I found there was only one culprit.

This was the credentials picker, which isn’t currently in the shared WinRT Core.

using Windows.Security.Credentials.UI;
CredentialPickerOptions opts = new CredentialPickerOptions();

This is the awesome bit, apart from that everything else just worked! That’s another 1.4k+ lines of shared code.


Once again I jumped back to the Windows 8.1 app and pressed F5 and was happy to see the existing app still working well, with its new projects and shared core.


Next – Build the Windows Phone 8.1 Project


I switched over and tried to build the Windows Phone 8.1 Project, the errors quickly stacked up and I had another “Oh this is going to be tough” moment.

Actually it wasn’t, in step 2 I moved some stuff to the shared project. The odd one here is that any references required for this code need to be referenced in both the Windows Phone and Windows 8.1 project. This is because, as I mentioned, the Shared bit isn’t actually a project, it’s a bunch of files and as such it doesn’t have references.

Now normally I’d just jump on nuget to get hold of these references, which is where the second bit of trouble struck …


I’d used the Prism for Store Apps package for a number of things in the Win8.1 app. When I tried to add it from Nuget I got some nasty red telling me it wasn’t supported by this project type.

I thought to myself, now WinRT is basically shared I wonder if I can use the Store version. Sure enough add it manually and you’re golden!


The second roadblock I hit was around App Insights, I couldn’t get this to play nice with Phone 8.1. However as I’m using a nice Pub/Sub model for events I can just leave this be for the time being while they’re SDK gets updated.

I will look to switch out the “AppInsightService” below with a WinPhone friendly one once it becomes available.


public class AppInsightService
       public AppInsightService()
           EventPubSub.Subscribe<CurrentPlaylistUpdate>(x =>
               var properties = new Dictionary<stringobject>() 
{ { "artist", x.CurrentPlayingTrack.artist }, { "track", x.CurrentPlayingTrack.title }, { "id", x.CurrentPlayingTrack.itemid } };
               ClientAnalyticsChannel.Default.LogEvent("Updated Song", properties);


So I started a little platform specific folder in my Win 8 Project. Now containing app insights and ApiAuth, which uses the Credentials UI mentioned earlier.



Then I had some fun sorting out some more references from the Windows Phone Side, I used Unity for my decency dependency injection and needed to get this up and running in the Phone Project. Again I saw issues with Nuget not playing nice with the new Project type.

So I jumped into my “packages” file and found the NetCore45 version that was currently used in the main Windows 8.1 App.


Adding this manually and again I was all good!


Unity and Next set of errors….



In my Windows 8.1 App I have a static reference to the Unity container in the App.xaml.cs. Rightly or wrongly I configure the container in the App.Xaml.Cs and use this to keep a static reference to it while the app is running.

I could see my Windows 8.1 Project building fine but not my Windows Phone project. This was because, as the Win8.1 builds, it pulls in the shared files from the new Shared area and all the references to “App.Container” are present in its App.Xaml.Cs.

When I build the Windows Phone 8.1 the errors appear as the Phone project doesn’t have that container setup in its app.xaml.cs. This was a good lesson, be careful when using static stuff which hangs off the App object in your shared section, as you’ll have different versions in each project!

Actually, in this case, it’s a nice thing as it makes perfect sense to have different Unity config for each app. For example, one of the items that unity resolves in my ApiAuth.cs – which we’ve had to move into platform specific folder in the Windows 8 Project as it couldn’t be shared. So in each App.Xaml.Cs I can have different unity config which provides a Platform specific version of that class.



Next tricksy one is navigation, as you can see from these error messages I’m using a static reference to the rootframe to move around. This isn’t going to do the trick, as we’re going to have different types depending on which version we’re in because the Pages don’t sit in the Shared Section.




My first thought here was to use Unity, as I’ve already got the way paved for me. I was going to implement a quick Interface and use the unity configuration to inject a WinPhone of Win8.1 Navigation handler in each of the projects. That way I drop this nasty stuff and I can map a navigate event to a different page based on the platform etc.

When I thought about it a bit more though I decided to go with leveraging the existing publish subscribe model, with services, I’m using in the app.

I created a “NavigationEvent” with “param” and “PageName” then a service which subscribes to these events and kicks off the navigation events.


namespace HyperM8.Shared.PubSub
    public class NavigationEvent
        public string PageName { getset; }
        public string ParamsString { getset; }

This led to changing around 5 or 6 of my commands to using this model.

var navEvent = new NavigationEvent(){ PageName = "MoreItemsPage", ParamsString = string.Format("{0},{1}", url, blog.sitename)};


VS the existing direct reference to the rootFrame to move around.

App.RootFrame.Navigate(typeof(MoreItemsPage), string.Format("{0},{1}",song.PlaylistUrl, song.SongCategory));


(What I also realised, during this process, was that I should be injecting my pubsub bus “EventPubSub” as an Interface so I can mock it out and test with something like MOQ. So a side effect of some of this refactoring was that I ended up breaking some of my tests.)

Next step was to implement the navigation service in the platform specific folder on the Windows 8.1 project.

I’m using a nice bit of functionality in Unity here called AllClasses. This allowed me to interrogate the classes loaded in the application and find a type that matched the “PageName” passed into the “NavigationEvent” then navigate to that page.


public NavigationService()
    EventPubSub.Subscribe<NavigationEvent>(navEvent =>
        var type = AllClasses.FromApplication().Where(c => c.Name == navEvent.PageName).FirstOrDefault();
        if (type == null)
            Debug.WriteLine("Failed to navigate to {0}, type not found", navEvent.PageName);
        App.RootFrame.Navigate(type, navEvent.ParamsString);

(@robgarfoot has pointed out that this is quite a bit of overhead, going through every class in ever assembly in the app each time a nav event is fired. So far I haven’t seen a huge hit from this but I do agree this is a bit smelly. When I have a bit more time I’m going to look at using Unity to make this a once time mapping, rather than something that happens every time the app navigates)

So with this now in place and all the commands updated, my project builds and my Windows 8.1 app is still working nicely. What I then realised was that I could put this “NavigationService” into my Shared section and as long as I named the pages correctly it would all work and also be shared.



I’ve shared a HUGE AMOUNT OF CODE and I’m way ahead where I would have been if I’d tried this before this updated. The only bits where I saw issues was with Navigation, Nuget Packages, References and Credentials Picks… none of which took me more than 15mins each to get around…


In short…. THIS IS AWESOME!!


My project structure is as follows, unloaded have either been killed by my changes or legacy.



Next up was migrating some of the XAML for the HubPage. Certainly there are more differences here. I got a massive helping hand from the new approach to Universal apps and project. I took a chance and moved my Resource Dictionary, containing styles and Data Templates, into the Shared Project.



Next I updated the app.xaml in both Win8.1 and WinPhone to pick up these styles and merge them into the dictionary. (Yes, there is a file called MupetStyles. No, I don’t have a clue why I called it that either).


<Application x:Class="HypeM8.App" xmlns="" xmlns:x="" xmlns:local="using:HypeM8">
                <ResourceDictionary Source="StandardStyles.xaml" />
                <ResourceDictionary Source="MupetStyles.xaml" />


To my absolute delight, this worked and my styles came across. Emboldened by this I picked up the body of my existing Windows 8.1 HubPage.xaml and Ctrl-C, Ctrl-V’d it into a page on the phone. With the exception of about 15 errors relating to slight differences in the XAML, THIS ALSO WORKED! I EVEN GOT MY NICE DESIGN TIME EXPEREINCE!

Just to emphasize this, I’d shared all my converters, styles and most of the page XAML between the projects. I still am completely blown away by this!


I was now at the stage where my app was building, had a working design time view and also nearly everything was shared (API, Converters, Services, Styles, ViewModels…)

Next – F5 onto the Emulator and see if it works for real


So by this point, if you’re anything like me, you’re thinking it’s all going to go wrong. And it did for a little bit, I came up against this cryptic little error while working with a message dialog.


After about 20mins of trying out different stuff I worked out that this actually means “MessageDialog” with more than two buttons isn’t supported on the phone 8.1. With that all ironed out I eagerly awaiting the next F5.

There I was, my app ported over with the first page up and running. Sure I needed to do some work on tweaking styling, porting other xaml pages and implementing a login screen but apart from that I was there. I’d shared nearly 2k lines of code and got to this point inside 2 days.

Hopefully this was a good guide for others trying to do the same, keep an eye out for HypeMix in the Windows Phone 8.1 Store once I’ve tweaked the styling and finished the rest of the pages. Depending on how I get on I may do a follow up post.



Windows Store App – Infinite Scrolling list with Xaml

I recently came across a great interface and behavior in windows 8.1. If you implement ISupportIncrementalLoading on your bound property then bind up to a gridview you’ll get infinite scrolling for free.

Below is an example from my HypeMix app where I pull in more tracks and add more to that list as the user scrolls, hopefully useful to others.

Tagged , ,

Azure Store – Free MongoDB, New Relic, SendGrid and more..

Hi All,

I set about to put together a new app and challenged myself to do the whole architecture on azure without spending a penny. The only caveat I set was that I should be able to scale if everything goes really well.

So the basic components I’m using are:

  • MongoDB – 500mb db offered on Azure Store by MongoLabs (having not played with mongo wanted to give it a go, you could also use SQL Azure free db or others)
  • SendGrid – 20k emails a month
  • New Relic – Free edition
  • Azure Websites – Free site

I was amazed hat you can get so much for free, I can basically stand up a monitored, scalable architecture with no outlay and then look at scaling as needed – based on the success of my services.

This is a great proposition for any entrepreneurial devs out there, grab the tooling and put your app together with no running costs while it gets off the ground!

Have a look around here:


Clean up unused Services from Azure Portal with PowerShell

So I’ve recently been using lots of VM’s and I end up getting through them fairly quickly – deleting and creating them regularly.

What I ended up with was loads of ghost services in the portal that were, once upon a time, associated with a VM in the distant past.

Given PowerShell is awesome, I set about automating the removal of these using the azure cmdlts. The trick is that I don’t want to remove services or VM’s that are currently “Stopped Deallocated” only those ghost services.

The script has three stages:

  1. Find all VM’s and their associated services.
  2. Find all the services without active deployments.
  3. Identify if any of these empty services have VM’s associated with them.
  4. Perform remove action on these services.

Start and Stop Azure VM’s (and more) in Parallel from Powershell

So I’ve got a demo that I’ve put together that uses a LOAD of Azure VM’s to demonstrate scripting against them.

To make sure I don’t get charged for them while I’m not using them I’ve got the following powershell to start and stop them:

Get-AzureVM | Stop-AzureVM –Force

Get-AzureVM | Start-AzureVM

I notice that this took a longer than I was expecting and so I started to do some digging. It turn out the PowerShell pipeline is executing these API requests in a synchronous way. Firing off the first request, waiting for the response and then, when completed, moving on to the next. This wouldn’t be a problem if I didn’t have loads of VM’s!

So I wrote the following, it uses PowerShell Jobs (think Task<T> if you’re a C# person), to kick these off as background jobs that run in parallel. (nb. You have to pass the variables in as arguments to the script block)


Now we get this lovely output. These all run as individual jobs and complete asynchronously, we then wait for all of them (think WaitAll() for C#). Now I can start all of my machines in the demo really quickly!

This is really useful in other scenarios too, think of any time you’re waiting on azure management API and the actions could be done simultaneously.

Id     Name            PSJobTypeName   State         HasMoreData     Location             Command

–     —-            ————-   —–         ———–     ——–             ——-

22     Job22           BackgroundJob   Running       True            localhost            …

24     Job24           BackgroundJob   Running       True            localhost            …

26     Job26           BackgroundJob   Running       True            localhost            …

28     Job28           BackgroundJob   Running       True            localhost            …

30     Job30           BackgroundJob   Running       True            localhost            …

RunspaceId           : 88465362-c8ce-45de-866d-9ced85cc3e40

OperationDescription : Start-AzureVM

OperationId          : 60712d20-311b-6cd5-b0df-9a750f024d0c

OperationStatus      : Succeeded

RunspaceId           : 3a9e93cf-7d16-4a2c-aeb7-4493e8ec8abb

OperationDescription : Start-AzureVM

OperationId          : fb494c0c-3728-62d4-b288-b8d391ad32d7

OperationStatus      : Succeeded

RunspaceId           : c1144e74-ba7c-4aa3-bcbb-aa9f2bd72fdf

OperationDescription : Start-AzureVM

OperationId          : 194254da-be36-6c7d-a147-67a980816c8e

OperationStatus      : Succeeded

RunspaceId           : 44af74a2-fc11-4e9b-8158-d9d84dd49d9e

OperationDescription : Start-AzureVM

OperationId          : 86059d5d-22ee-6a55-871d-28bcf52241a2

OperationStatus      : Succeeded

RunspaceId           : a44b51e9-11cc-4d31-875e-5e0fd16b935a

OperationDescription : Start-AzureVM

OperationId          : d4e2fcce-b270-6d6e-ad0c-8322e2c4df23

OperationStatus      : Succeeded

PaperBoy update Coming soon… awaiting certification

Hi All,

I’ve finally got around to dedicating some time to paper boy over Christmas.

Change Log:

  • Fixed offline reading functionality (also now allow you to download just one or all feeds). More work is coming on this to rework it for speed and reliability also UI isn’t perfect at the moment. *Edit: may still have some issues, under testing some came up.
  • Updated reader view to be nice and like it used to be (this is experimental at the moment)
  • Included switch view button to use Readability mobilizer
  • Updated swipe between articles – smooth and nice now
  • Reinstated font size control from settings page
  • Fixed feed selector to remember previously selected feeds

*New reader view looks like so*


Hopefully more updates coming soon too, if all goes well!

Stand up a SQL AlwaysOn Cluster on Azure IAAS in One-click

Hi All,

I had a play with AditiCloud’s Brewmaster today to see what it can do. The basic idea is that you can quickly deploy one of their templates for SQL, Active Director etc into your Azure IAAS subscription.

I picked SQL Always On Availability cluster, which if you’ve ever tried to do manually is a bit of pain, and set it off to do it work. After some simple config, name etc, I clicked go and went to get some breakfast.

You get a really nice view of progress in the browser, powered by signalr no less, and then once complete you can click “my deployments” and get all your login details.

All came up well and I had my cluster up and running inside 40mins with one-click, I’m very impressed and will likely use this again when setting up demo environments in the future. Link and some screenshots are below.



Using LinqPad to query Azure Diagnostics (Best WAD viewing client for Devs imo)

Hi All,

Really quick and simple post. In a normal windows azure cloud service you get all your lovely eventlogs put into table storage for you to use when diagnosing issues.

Unfortunately that can be a bit daunting as there isn’t, or I didn’t think there was, a handy client to view them all in.

With the AzureTableStorage driver for LinqPad I can quickly write complex and simple queries to integrate all the WAD logs and I get lovely intellisense in a nice familiar interface.

from items in WADWindowsEventLogsTable
 where items.Timestamp > DateTime.Now.AddMinutes(-10)
 where items.Role == "ControllerRole"
 select new { time = items.Timestamp, desc = items.Description}

And I’m straight to the root of the problem, or near enough.


MOLAPSE – Timelapse App for Movember

Hi All,

I’m looking for some volunteers with a variety of devices to test out ‘molapse’, all will need front facing cameras.

“Capture your brilliant bushy beard as it mogresses through movember with molapse. It’s a timelapse app focused on those who’ll be taking part in Movember.

If you want to help out then drop me an email at info[at] and include your liveid, I’ll send out a beta once I’ve got a few people signed up.

Flurry Stats Windows Phone client

Hi All,

I wrote this a while back for myself and finally got around to polishing it enough to release into the store.

It’s a really basic app which will connect to your flurry account and show you new users and number of sessions while your out and about!

1 of 1


Get every new post delivered to your Inbox.

Join 263 other followers