The code you never maintain has a maintenance cost of zero.

If you tried it before you might want to give it another shot. There are a lot of improvements and it is much more useable overall. Here is a screen shot of the new UI:

Here is a list of some of the new features:

• 3 months free trial, $1.29 to purchase.
• Current maneuver shows an icon rather than the full maneuver text.
• Easier to read maneuver text at top of screen.
• Preview the entire route with simple forward and back buttons.
• An estimated time of arrival is displayed.
• Quick reminders when approaching a maneuver on long routes.

Bug fixes:

• Fixed a bug where it would randomly think you were off route.
• Fixed a sensitivity bug where it would think you were off route on a wide road.
• Fixed a bug where entering the route from somewhere beyond the first maneuver would not put you on route.
• Various stability fixes.
• Added a screen for sending me crash reports directly when unexpected errors occur.

Overall it’s a much more stable and useable version. If you give it a try and  have any feedback please let me know!

Never spend a minute doing a task that you can spend the rest of your life automating.

When you have one thing, you need one hand.  When you have two things, you need two hands.  When you have three things, you need a database.

Download:

It’s ok for two threads to modify the same value at the same time, so long as both values are correct.

I also use this mechanism to forward the user to a page to ask them to allow or deny the app rights to use the location services the first time its loaded up. This resulted in a strange case where I was actually redirecting the user to a page other than what they were actually navigating to. When I then attempted to navigate them to the correct page it ended up being a no-op since the current page was at the top of the navigation stack as the uri I was attempting to navigate to. In other platforms the NavigationService has a Refresh method you can call to resolve such problems but in Windows Phone 8 it is mysteriously missing. So after wasting a couple hours I managed to find a way to resolve this cunundrum.

Simply create a page in your application called Refresh.xaml and Navigate to this page. Something like this:

private void OnAllowClick(object sender, RoutedEventArgs e)
{
  LocationService.AllowLocationServices = true;
  this.NavigationService.Navigate(new Uri("/Views/Refresh.xaml", UriKind.Relative));
}

Then in Refresh.xaml you simply pop the last item off the navigation stack and navigate back to it:

public partial class Refresh : PhoneApplicationPage
{
  public Refresh()
  {
    InitializeComponent();
  }

  protected override void OnNavigatedTo(NavigationEventArgs e)
  {
    var j = this.NavigationService.RemoveBackEntry();
    this.Dispatcher.BeginInvoke(() => App.RootFrame.Navigate(j.Source));
    base.OnNavigatedTo(e);
  }
  
  protected override void OnNavigatedFrom(NavigationEventArgs e)
  {
    this.NavigationService.RemoveBackEntry();
    base.OnNavigatedTo(e);
  }
}

This will refresh to the current uri and preserve the navigation stack correctly.

It turns out all you have to do is to make the extension available via http then create an ATOM feed for your extensions. I just dropped a static atom.xml file onto a webserver on my backup dev machine and update it manually when I get a new build of the extension and presto! You just give your team the URL and they can configure VS to also look at that URL when searching for extensions.

Here is the structure of the atom XML you need to create in your feed to make it work:

<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text"></title>
  <id>uuid:7d461a9c-df42-4fc3-bb84-b83c5147e145;id=1</id>
  <updated>2012-11-06T22:19:45Z</updated>
  <entry>
    <id>2bde3d56-7ac0-4d8d-8ae8-794b631b0b27</id>
    <title type="text">Example Extension</title>
    <summary type="text">An example of hosting a VS extension for my team.</summary>
    <published>2012-11-02T10:43:32-05:00</published>
    <updated>2012-11-06T11:31:29-06:00</updated>
    <author>
      <name>Microsoft</name>
    </author>
    <content type="application/octet-stream" src="Example.vsix" />
    <Vsix xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/developer/vsx-syndication-schema/2010">
      <Id>2bde3d56-7ac0-4d8d-8ae8-794b631b0b27</Id>
      <Version>1.2</Version>
      <References>Visual Studio MPF 11.0\Microsoft.VisualStudio.MPF.11.0\[11.0,);</References>
      <Rating xsi:nil="true" />
      <RatingCount xsi:nil="true" />
      <DownloadCount xsi:nil="true" />
    </Vsix>
  </entry>
</feed>

1. Up to 3 tests that take longer than 2 seconds.
2. Up to 100 tests that take longer than .02 seconds.
3. Infinite tests that take less than .02 seconds.

Syntactic sugar will give your code cavities.