In The Hand

Review: Making Embedded Systems (Elecia White)

PeterFoot — Fri, 20 Jan 2012 07:53:00 GMT

As an interesting addition, at the end of each chapter, there is a potential interview question for an embedded developer position. It’s an unusual idea but is a way of tying up the topics covered in the chapter. Because the book is written for developers it applies patterns and techniques which the reader will already be familiar with and how they apply to embedded systems.

It emphasises the need to be aware of the limited resources available and how to pare down operations to a minimum to make best use of them. It also talks about various options for input and output for a variety of peripherals and sensors.

The book offers a useful introduction to the world of embedded development to a developer with existing C (or similar) experience. More experienced embedded developers will probably want to delve into more detail on the specific areas, but this is a great starting point.

4/5

Review: Making Embedded Systems (Elecia White)

Peter Foot — Thu, 19 Jan 2012 19:53:00 GMT

This title takes a traditional software programmer into the world of embedded system. It covers the process of designing and implementing an embedded system from a sketch through to optimising performance and power consumption. As an interesting addition, at the end of each chapter, there is a potential interview question for an embedded developer position. It’s an unusual idea but is a way of tying up the topics covered in the chapter. Because the book is written for developers it applies...(read more)

Windows Phone Update due shortly

PeterFoot — Sat, 07 Jan 2012 01:32:00 GMT

Microsoft have published details of a new update (7.10.8107.79) which adds a number of fixes to the Mango release. It fixes the issue where the on screen keyboard will randomly hide itself which I've been finding frustrating recently and also a fix for the SMS bug which could disable messaging. It also hopefully finally resolves the issue when forwarding Exchange messages where the original message body would disappear. It hasn't shown up yet but expect it over the next couple of weeks. Full details on all the updates and fixes are published here:-

http://www.microsoft.com/windowsphone/en-us/howto/wp7/basics/update-history.aspx

Developer Unlock Expiry

PeterFoot — Thu, 22 Dec 2011 11:35:00 GMT

When you've developer unlocked your Windows Phone you can merrily deploy and debug on it and everything is great. If you've upgraded to Mango you had to run the Unlock tool again but this is fairly painless. What is not obvious is that the developer unlock has a 12 month expiry from when you first register the device and even when you subsequently use the unlock tool on the same device this never gets extended.

So one day you'll be developing as normal and get the error "Failed to connect to device as it is developer locked. For details on developer unlock, visit http://go.microsoft.com/fwlink/?LinkId=195284.". Instictively you launch the developer unlock tool, enter your App Hub credentials and unlock the phone. This completes with no errors but you'll soon find that it hasn't helped despite the fact you entered valid credentials and your App Hub account is valid.

The solution to this problem is to log into App Hub on the web and go to your account profile, select devices and remove the offending device from the list (here you'll see that the expiry date is shown). After doing this you can run the unlock tool again and successfully unlock the device.

Microsoft could certainly improve this process in the future by using a more descriptive error message and also by improving the unlock tool so that when you try to unlock a device that has expired it refreshed the registration and provide 12 more months of use (just like the manual process described above does).

Merry Christmas, and here's to a wonderful 2012 filled with Windows Phone goodness!

Submitting Apps to Marketplace with Background Tasks

PeterFoot — Thu, 08 Dec 2011 23:38:00 GMT

I've been working on an update to the Tasks application which adds in background synchronisation using the new background task support in Windows Phone 7.5. As with any app when you submit your XAP static analysis is performed on it to check, for example, that you have declared the correct capabilities based on the functionality in your app. Within a background agent you are only allow to call a subset of APIs - as you would expect you can't play sound effects or draw to the UI (with the exception of toast notifications and tile updates). Because the main app has to include a reference to the dll which provides the background task, and the functionality within the dll is used in both the background task and the main app it made sense to move all of the logic into the background dll. This meant including a number of third-party references. I was very careful to ensure that nowhere in the background task was any restricted API called and it worked perfectly in testing.

The first problem is that upon submitting the static anaylsis looks at all of the referenced dlls and sees that they contain APIs not permitted in a background task and blocks the XAP. One of the culprits was InTheHand.Phone.dll (Part of Mobile In The Hand) because it provides a mixture of helper classes for logic and for UI. As I've been working on the 7.1 version in tandem I've now split this into two assemblies for Windows Phone 7.1 SDK projects. This means we can continue to use InTheHand.Phone in background tasks and add a reference to the second assembly in the main application only.

The second problem is that code within the sync logic calls ScheduledActionService.Add which is disallowed within a background task. This API is used within Tasks to add system-wide reminders (Another new feature for this version) for new task items. The code also has the ability to update and delete reminders based on modified or deleted tasks but these do not seem to have been flagged up as errors. This is a pain because it means that if the device syncs a new task with a reminder set to show before you next open the foreground app we won't have had a chance to register it.

The other issue with the NeutralResourceLanguage is an issue with projects originally created with an older version of the development tools. You can add this setting from the projects properties, Application tab and click "Assembly Information...".

This has been an interesting learning experience and shows that the validation picks up not just APIs used in the background agent code-path but also in referenced assemblies.

Showing Mango Features on Marketplace

PeterFoot — Wed, 21 Sep 2011 08:30:00 GMT

The Windows Phone team have posted to their blog about application updates with a couple of useful points:-

From October you will again be able to publish updates to your 7.0 apps independently from 7.5 (previously once you had published a Mango update your 7.0 app would be locked). It does mean potentially being in limbo for a month but at least you are not stuck completely with no way of updating a 7.0 app. This is important as it will take some time before many users will have the opportunity of upgrading to Mango.

When submitting apps there is only one description for both versions of your app so you must describe which features are for Mango only. For the purposes of Screenshots there is now an officially accepted overlay which can be used to indicate Mango-only functionality. You can download a ZIP containing the overlay and examples here:-

http://create.msdn.com/downloads/?id=882&filename=Marketplace_7.5_Badges.zip

The full blog post is here:-

http://windowsteamblog.com/windows_phone/b/wpdev/archive/2011/09/20/submit-windows-phone-7-5-apps-today-update-7-0-apps-in-october.aspx?utm_source=twitterfeed&utm_medium=twitter

Showing Mango Features on Marketplace

Peter Foot — Tue, 20 Sep 2011 20:30:00 GMT

The Windows Phone team have posted to their blog about application updates with a couple of useful points:- From October you will again be able to publish updates to your 7.0 apps independently from 7.5 (previously once you had published a Mango update your 7.0 app would be locked). It does mean potentially being in limbo for a month but at least you are not stuck completely with no way of updating a 7.0 app. This is important as it will take some time before many users will have the opportunity...(read more)

Working with Marketplace Exported Reports

PeterFoot — Tue, 13 Sep 2011 01:14:00 GMT

When Microsoft refreshed the Windows Phone developer portal in advance of the Mango refresh they added various improvements to reporting, an important one being export to file (XLSX). When you open the exported payout detail reports in Excel and enable editing you'll see a number of warnings against a couple of columns. This is because the data is formatted as text but Excel recognises that the contents are numbers. In order to use these values in formulas or graphs you'll need to convert them to numerical values.

The easiest way I found to do this was to select an empty cell and Copy it, then select the entire columns of "Units Sold" and "Royalty", right click and select "Paste Special". From the popup select "Add" as the operation and click "Ok". Now all your number columns are really numbers (you'll see the formatting change to right alignment).

Need a Windows Phone developer handset?

PeterFoot — Tue, 28 Jun 2011 10:32:00 GMT

Are you a Windows Phone 7 developer in New Zealand? Are you in need of a real Windows Phone device to test and debug your apps on? If so I have a spare Samsung developer handset which is going free to a good home. Shipping is $5 to anywhere in New Zealand. I could ship it internationally but the cost would be higher. Contact me if you are interested. I have only one and it’s first come-first served!

Update - The phone has now been claimed

Finalists Announced for the Imagine Cup 2011

PeterFoot — Wed, 25 May 2011 21:37:00 GMT

I recently had the fun experience of working in the judging team for the Imagine Cup XBox/Windows Game Design competition. This was one of the many tracks of the Imagine Cup competition concentrating on games for Windows and XNA written by teams of students. The quality and variety of the submitted games was awesome and I’m pleased to see one of the titles I judged made it to the finals. You can read all about the final five games in this track here:-

http://blogs.msdn.com/b/andrewparsons/archive/2011/05/24/meet-the-finalists-xbox-windows.aspx

Quick Look at the Mango Developer Tools

PeterFoot — Tue, 24 May 2011 23:38:00 GMT

The Mango developer tools require Visual Studio 2010 and Service Pack 1. The package includes a Mango emulator image and new project templates. The tools allow you to work with (and create new) projects for Windows Phone 7.0 as well as 7.1 (which is how the tools describe the Mango release. Previous rumours had suggested 7.5. The full list of 7.1 project types is below.

There are no visible difference to the developer tools, you have the same XAML editor and code editors as before and the same Toolbox items.

New Functionality in Microsoft.Phone

Microsoft.Devices namespace now holds classes for working directly with the camera, allowing you to put a live viewfinder in your app and access and manipulate the raw data.

Microsoft.Phone contains a base BackgroundAgent class and the BackgroundAudio and BackgroundTransfer namespaces contain specific implementations for audio and file transfers.

Microsoft.Phone.Info adds new properties and a new way of accessing them. Rather than the GetValue/TryGetValue approach there is a DeviceStatus class with strongly typed properties. The new properties are:-

IsKeyboardDeployed (for devices with sliding keyboards)
IsKeyboardPresent
PowerSource (Battery or External)

There are events for PowerSource and IsKeyboardDeployed so you can monitor when these change.

Microsoft.Phone.Net.NetworkInformation (short and snappy!) exposes a lot more information about network connectivity. DeviceNetworkInformation exposes not just current network availability but also whether Cellular Data or Wifi are enabled. In the case of Cellular Data you can determine if the phone is roaming. This method also exposes the ability to dom a DNS lookup for a server. Via NetworkInterfaceList you can get a full list of all the network interfaces and their characteristics. Extension methods are provided for WebRequest and Socket classes so that you can specify which network you want them to use.

Microsoft.Phone.Notification contains some small improvements to the HttpNotificationChannel functionality. You can now query the connection status and monitor when it changes.

Microsoft.Phone.Scheduler contains classes for scheduled actions, either background tasks, timed alarms or system-wide reminders.

Microsoft.Phone.Shell adds improvements for tiles and the system tray. For tiles you can modify data locally without a round-trip to the notification server. You can also create secondary tiles for functionality within your application. The SystemTray finally lets you change the background color and also allows you to expose progress text or a progress bar in the system tray as the built-in applications currently can.

Microsoft.Phone.Tasks contains some new Launchers/Choosers:-

AddressChooserTask – Pick a mailing address from your contacts
BingMapsDirectionsTask – Get directions to a specific location
BingMapsTask – Center a map on a specific point
GameInviteTask – Start a multiplayer game
SaveRingtoneTask – Allow a user to save an audio file you provide to their ringtones on the phone

Microsoft.Phone.UserData contains classes to access (read-only) Contact and Calendar data on the phone.

Of course this is merely scratching the surface. These improvements (especially features like background tasks) open up whole new possible features in our apps!

Download the tools now : http://www.microsoft.com/downloads/en/details.aspx?FamilyID=77586864-ab15-40e1-bc38-713a95a56a05

Bug in Marketplace Over-The-Air Update

PeterFoot — Sun, 22 May 2011 05:08:00 GMT

Recently we had an issue where our application would crash on launch after an update was pushed to the device through Marketplace. Fresh installations were not affected and we could not replicate the issue on a development machine. By analysing the contents of the two XAP files we found something very interesting. The application uses a number of dlls to provide various functions. The update made a number of small changes within the code but there was one clear difference in the dlls. One of the dlls in the newer version was an older version than in the previous XAP. While this was not entirely intentional it wouldn’t itself cause any problems as shown by the fresh install scenario working as expected. We therefore found that in the (albeit unusual) case of a XAP file containing an older dll it would not overwrite the newer dll on the device. This caused the app to immediately crash while it loaded – presumably a TypeLoadException.

This is quite a rare scenario and probably explains why the bug hasn’t been seen more frequently. Luckily there is a workaround when you know about it. If you have to roll back the functionality in a component of your application make sure you still increment the version number. If the dll is from a third-party and out of your control this is still a problem. Hopefully this is something which can easily be fixed in a phone update. While I understand it is a rare scenario and probably explains why it hasn’t been tested, I still consider this a bug as the application package as shipped in the XAP is what has been tested as a complete package (both by the developer and during Marketplace ingestion) and should be considered the latest version as a whole regardless of the versions of individual files.

APPA Mundi Tasks 1.9

PeterFoot — Thu, 21 Apr 2011 16:20:12 GMT

The latest version of our Tasks app has now hit Marketplace. This release builds on the improvements from my last blog post:-

We now have fixed an issue some users were encountering with synchronising Hotmail tasks in v1.8
We now support a wider range of Exchange Server 2003 mailboxes including those with non-standard security policies
Thanks to user-feedback we’ve improved the French and German text within the application
We’ve changed the timing of how the welcome message pops up in the trial version to avoid navigation issues
Based on user feedback we’ve added the option of putting undated tasks at the top or bottom of your To-Do list
Since version 1.7 we’ve changed the transition animations between pages to match the built-in applications (obviously this doesn’t come across in the screenshots!)

We’d like to say thanks for all the great feedback we’ve received from users. We’ll keep listening and adding to the product so keep it coming!

Managing Processes and Memory With Mobile In The Hand 7.0

PeterFoot — Tue, 19 Apr 2011 15:38:03 GMT

.NET Compact Framework

The Compact Framework provides the capability to start a separate process from your code, and stop it but it doesn’t give you more detailed information about what is running and what components are in use. Windows CE includes the optional ToolHelp component (present in all Windows Mobile versions). The InTheHand.Diagnostics namespace includes a number of classes for working with ToolHelp in a way which matches the full .NET Framework. The ProcessHelper class includes the GetProcesses() static method to return all running processes on the device. Extension methods GetModules() and GetThreads() return ProcessModule and ProcessThread collections for a specific Process.

ProcessModule exposes name, size and version information for an individual module. ProcessThread exposes id, priority and elapsed processor time.

Another way you might want to interrogate a process is to determine the memory usage. For your own process we’ve followed the Windows Phone model and so InTheHand.Phone.Info.DeviceExtendedProperties.ApplicationCurrentMemoryUsage

provides you this useful figure as a strongly-typed property. It is also accessible from the GetValue method as you would on Windows Phone.

Windows Phone

Other than the built in set of tasks you can’t start any other applications or tell if they are running. You do have access to memory statistics though which are accessible from the Microsoft.Phone.Info.DeviceExtendedProperties class. A limitation here is that if you use this method to get the memory statistics your app will automatically get marked as requiring the ID_CAP_IDENTITY_DEVICE capability which it doesn’t actually need for these properties. We built a helper class for two reasons – firstly to remove this requirement and secondly to provide strongly-typed properties as an alternative to the GetValue implementation. On Windows Phone therefore you can use:-

InTheHand.Phone.Info.DeviceExtendedProperties.ApplicationCurrentMemoryUsage

InTheHand.Phone.Info.DeviceExtendedProperties.ApplicationPeakMemoryUsage

and

InTheHand.Phone.Info.DeviceExtendedProperties.DeviceTotalMemory

Mobile In The Hand 7.0

Mobile In The Hand is a suite of components for developing mobile applications across Microsoft’s various mobile and embedded operating systems. It will save you development time and allow you to share more code across different .NET project types.

Geocoding and Reverse Geocoding with Mobile In The Hand 7.0

PeterFoot — Fri, 15 Apr 2011 19:00:35 GMT

This is the first in a series of posts about Mobile In The Hand 7.0 which brings a collection of reusable components to the .NET Compact Framework. This latest version is updated to support all versions of Windows Mobile including Windows Embedded Handheld, All versions of Windows Embedded Compact (in it’s various names) from 4.1 to 7.0 and a set of companion libraries offering a subset of the functionality on Windows Phone 7.

When the .NET Framework 4.0 was released it introduced a new namespace – System.Device.Location which provided a range of location features. Subsequently this was used as the model for Windows Phone’s APIs. One major whole in the Windows Phone implementation is that the CivicAddressResolver is not implemented and doesn’t return a result. Mobile In The Hand 7.0 comes to the rescue with a two pronged attack:-

An InTheHand.Device.Location.GeoCoordinateWatcher for the .NET Compact Framework. This uses the GPS Intermediate driver present on all Windows Mobile 5.0 and later devices and available as a system component on Windows CE 6.0 and beyond. This is exposed with a familiar object model which matches that found in .NET 4.0 and Silverlight for Windows Phone.

Secondly two new components are provided – BingCivicAddressResolver takes a GeoCoordinate and uses Bing Maps to resolve a CivicAddress object similar to the functionality available on desktop windows. Additionally as an extra feature the BingGeoCoordinateResolver allows you to resolve a GeoCoordinate from an address or partial address. Both of these classes are provided in the .NET Compact Framework and Silverlight for Windows Phone libraries which make up Mobile In The Hand 7.0. The Compact Framework version offers both Synchronous and Asynchronous calls, the Silverlight version just exposes the Asynchronous calls.

Tasks: Coming in v1.7

PeterFoot — Wed, 06 Apr 2011 22:59:41 GMT

This week we released the second in a couple of updates to the Tasks application. We’ve added a large number of features and improved compatibility with a wider range of servers based on user feedback. Let’s look first at compatibility – we now support Exchange 2003 and other ActiveSync 2.5 compatible servers. This includes your Hotmail To-do list! We received feedback that a lot of users still had Exchange 2003, one of the main reasons for this is that this was the last Exchange version to support a 32-bit OS and many people have 32-bit Windows Server 2003 and Small Business Server 2003 machines which they have no immediate plan to replace.

Trial Version

The next common piece of feedback was in the functionality of the Trial version. we’ve removed the restriction on the number of Tasks which the application will sync. Because the app used to synchronise the first 10 tasks these were rarely the latest and most useful tasks to have on your phone. The trial app is now limited to run for 7 days to let you evaluate the application.

New Features and Fixes

We have improved the logic behind our live tile so that it’s updates should appear in a more timely manner. When it receives an update it also uses your chosen accent colour:-

We’ve made numerous tweaks to the user interface within the application too. We also respect your theme colour throughout the application, and have added some new transition animations between pages which closely match the experience in the built-in Email and Calendar applications which Tasks is designed to complement. We’ve made category editing easier by using a picker control to easily select existing categories as well as support for adding new categories.

We’ve had support for editing Reminders on the phone in the last couple of versions but we’ve now added reminders within the application. When you launch the application it will display currently due reminders and others will pop up as they become due when you are using the application.

We’ve added support for completing recurring tasks and the application will show both the completed instance and the next task in the pattern (if applicable).

Thanks to feedback from several users we’ve also made improvements to the localised text – yes the application supports all Windows Phone languages (US English, UK English, French, German, Italian and Spanish).

We’ve also made numerous bug fixes and some performance improvements. There were some issues around sorting, specifically where several tasks had blank subjects, these are now resolved.

Exchange 2010 Synchronisation Fix

One issue we have encountered can be observed if the app shows “initializing…” and then immediately “synchronization failed” when you try to sync. This seems to be specific to Exchange 2010 and can be resolved by removing the device from your Exchange account using Outlook Web Access and then resetting synchronisation. From OWA click Options and “See all options…” then select Phone in the left-hand list. You’ll see a list of mobile devices attached to your account. Your Windows Phone will have an entry and the Tasks application will have a separate one. To find the correct device select one and click Details. You can identify Tasks because it will show the user-agent as APPA-Mundi-Tasks/x.x.x.x where x.x.x.x is the version number.

Once you’ve identified the correct device delete it from the list, log out of OWA and from the Tasks application go to the Settings page and click Reset. The application can now setup a new sync relationship.

Windows Phone 7: Localisation and Windows Phone Features

PeterFoot — Tue, 05 Apr 2011 11:45:27 GMT

Anyone who has built an application for Windows Phone 7 in multiple languages will know there are three parts to the process. Within your application you can use managed RESX resource files to provide localised strings. For your application title or the initial text for your Live Tile you must use native resource dlls. Then when you are ready to submit your application to Marketplace you’ll need to provide descriptions, keywords and screenshots tailored for each supported language. At the moment there are six possible languages on the device side:-

English (United States)
English (United Kingdom)
French
German
Italian
Spanish

On Marketplace there are five languages – English (International) is used to cover both variants above. Even if your icon is standard across all languages you still have to submit it with each language as you upload to Marketplace.

There are several ways you can get your text translated, however one thing we noticed from experience is that certain features have established names in these different markets which may not equate to a direct translation from the English. Because the emulator and all retail Windows Phone 7 devices support all six languages you can easily change your device language and see how your application looks.

Feature names

For my future reference (and for yours) I’ve included a table below of some of these which may be useful. As I compile a list of more common words and commands I’ll add them to the table:-

English	French	German	Italian	Spanish
Start screen	Écran Démarrer	Startseite	Start Screen	Pantalla Inicio
Live Tiles	vignettes dynamiques	Live-Kacheln	riquadri animati	ventanas vivas
People	Contacts	Kontackte	Contatti	Contactos
Pictures	Photos	Bilder	Foto	imagenes
Games	Jeux	Spiele	Giochi	Juegos
Marketplace	Marketplace	Marketplace	Marketplace	Marketplace
Email	E-mail	E-Mail	E-mail	Correo electrónico

Common Controls

See also my previous post with localised resources for the Silverlight Toolkit which localises the Date/Time pickers and ToggleButton controls. This also works with the latest February release of the toolkit, simply use this destination folder:-

C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.0\Toolkit\Feb11\Bin

The exception which proves the rule

Finally another observation which is specific to German. While the UI normally displays pivot headers and toolbar/menu text in lower-case this is not true for German where items should be capitalised.

Windows Phone 7: More Tilt Effect

PeterFoot — Tue, 29 Mar 2011 13:14:09 GMT

The Silverlight Toolkit for Windows Phone (Latest version is February 2011) contains a Tilt Effect implementation. To add it to your controls requires the addition of an XML namespace definition and one dependency propery set in your page XAML.

<phone:PhoneApplicationPage

…etc…
xmlns:toolkit="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls.Toolkit"
toolkit:TiltEffect.IsTiltEnabled="True">

However the implementation doesn’t apply the effect to all the same places as you will find it in the native application. So far I’ve identified the ListPicker and MenuItems within the ContextMenu control. You can add additional types to receive the Tilt effect and I’ve raised an issue in the CodePlex project so hopefully this will be addressed in the next update. In the meantime you can add the following to your App constructor:-

TiltEffect.TiltableItems.Add(typeof(ListPicker));
TiltEffect.TiltableItems.Add(typeof(MenuItem));

By itself I found that this didn’t actually fix the ContextMenu and the items do not tilt as they do in built in applications. However all is not lost! If you apply the property to each entry in your ContextMenu it does use the feature:-

<toolkit:ContextMenuService.ContextMenu>
   <toolkit:ContextMenu>
      <toolkit:MenuItem toolkit:TiltEffect.IsTiltEnabled="true" Name="firstMenuItem" Header="edit" Click="FirstMenuItem_Click"/>
      <toolkit:MenuItem toolkit:TiltEffect.IsTiltEnabled="true" Name="secondMenuItem" Header="delete" Click="SecondMenuItem_Click" />
   </toolkit:ContextMenu>
</toolkit:ContextMenuService.ContextMenu>

Once you’ve done this you’ll have a context menu which behaves closer to the built in control. The Silverlight Toolkit is a great resource for additional controls and features which are not present in the Windows Phone 7 SDK. As always I’m eagerly awaiting the next update!

When Phone Tasks Might Not Work

PeterFoot — Sun, 27 Mar 2011 13:50:19 GMT

The range of Tasks available in the Microsoft.Phone.Tasks namespace call into various system features from your application. In some circumstances these may not work as expected. The most obvious example is the Emulator where not all of the system is implemented. The behaviour will differ depending on the specific task. For example EmailComposeTask on the emulator will display a message that no accounts are setup and of course you cant create these yourself because this functionality is hidden in the emulator. The other situation which can cause tasks to fail is when your device is docked with the Zune software. As a developer there is a tool to get around this when debugging but you must write your software to be aware of this to avoid upsetting users. In Windows Mobile we would have used SystemState.CradlePresent to detect when the device was docked, there isn’t an equivalent property for Windows Phone. Instead you can check the network type. Because we know that the hardware configurations for Windows Phone 7 are quite specific we know that devices will have phone, wifi and USB cable connections. You can detect the network type using the Microsoft.Phone.Net.NetworkInformation.NetworkInterface.NetworkInterfaceType property. There are a lot of possible values in the NetworkInterfaceType enumeration but only a few are relevant:-

Ethernet – Used for Zune cable connection

MobileBroadbandCdma

MobileBroadbandGsm – For phone connections

Wireless80211 – For WiFi

So by checking for the value Ethernet we can tell if the device is currently docked. The only caveat is that this property isn’t set immediately when you dock and there can be a few seconds before the connection is established.

Case Study – PhotoChooserTask

The PhotoChooserTask works on the emulator with a selection of default images. On the phone it will fail if the phone is docked. The Completed event will be raised and a TaskResult of Cancel will be returned – as if the user had cancelled. This simple block of code can be used to wrap your call and handle this situation (for a change a little VB):-

If Not Microsoft.Phone.Net.NetworkInformation.NetworkInterface.NetworkInterfaceType = Microsoft.Phone.Net.NetworkInformation.NetworkInterfaceType.Ethernet Then
            Dim pct As New Microsoft.Phone.Tasks.PhotoChooserTask
            AddHandler pct.Completed, AddressOf pct_completed
            pct.Show()
Else
            MessageBox.Show("To view photos, disconnect your phone from the computer", "My Application", MessageBoxButton.OK)
End If

Task behaviours

Task Name	Emulator	Phone (Docked)
CameraCaptureTask	Yes (simulated data)	No (Completed returns TaskResult.Cancel)
EmailAddressChooserTask	Yes	Yes
EmailComposeTask	Shows error message (no account)	Yes
MarketplaceDetailTask	Exception 80070057	No
MarketplaceHubTask	Exception 80070057	No
MarketplaceReviewTask	Exception 80070057	No
MarketplaceSearchTask	Exception 80070057	No
PhoneCallTask	Yes	Yes
PhoneNumberChooserTask	Yes	Yes
PhotoChooserTask	Yes (Sample data)	No (Completed returns TaskResult.Cancel)
SaveEmailAddressTask	Yes	Yes
SavePhoneNumberTask	Yes	Yes
SearchTask	Yes	Yes
SmsComposeTask	Yes	Yes
WebBrowserTask	Yes	Yes

The marketplace tasks perform no action and these ones don’t have a Completed event so you don’t get any feedback. You can provide similar logic to the above to warn the user that they can’t use Marketplace functionality when docked, you could also hide any marketplace links from your UI based on the network state.

Silverlight for Windows Phone Toolkit–Feb 2011

PeterFoot — Fri, 18 Feb 2011 13:32:39 GMT

The latest release of the Silverlight Toolkit contains a number of fixes and new features including:-

TiltEffect (previously available separately)

PerformanceProgressBar (previously available separately)

Visual Basic Samples

Major improvements to LongListSelector and Transitions

Go grab the latest release here:-

http://silverlight.codeplex.com/releases/view/60291

Copyable TextBlock for Windows Phone

PeterFoot — Tue, 08 Feb 2011 22:31:49 GMT

The latest update for Windows Phone 7 adds automatic support for Copy and Paste to TextBox controls in your application. By default this means you can’t copy text from static TexBlock controls. There is however a solution which requires minimal changes to implement. You have to replace the TextBlock control with a TextBox and set the IsReadOnly property to true. At first glance this will totally ruin the look of your application – even if you set custom background/foreground colours the control will display in grey on grey when IsReadOnly is true. It is possible to change this behaviour by applying a custom template to the control. Originally I did this in Blend but I found it had generated much more XAML than absolutely necessary so I set about removing redundant parts to result in this:-

Simply add this to the Resources collection for your page.

Then your TextBox is customised like so:-

The result looks and behaves like a TextBlock and still follows your system theme but allows copying on the latest emulator:-

I created a sample project with all of the code showing the different behaviours of the TextBlock, read-only TextBox and customised TextBox which you can download here:-

http://appamundi.com/files/uploads/CopyableTextBlock.zip (44kb)

Tasks Frequently Asked Questions

PeterFoot — Tue, 25 Jan 2011 13:41:41 GMT

Since we have released a couple of updates for the application we have updated the Frequently Asked Questions for the Tasks application and moved them to a new location:-

http://appamundi.com/tasks-faq/

If you have any issue with the application or question this should be your first port of call. If your issue is not described here please send us an email with as much detail describing the issue as possible and we will work with you to resolve it.

Finally remember we do provide a Trial version of the application which lets you test whether the app works with your specific Exchange Server configuration.

Win a Windows Phone 7 LG E900

PeterFoot — Mon, 24 Jan 2011 09:05:34 GMT

Following my review of the LG E900 handset we have the opportunity for one lucky winner to get a Windows Phone 7 of their own. All you need is a little creativity and this handset could be on its way to you! See the contest page for the full details:-

http://appamundi.com/win-a-windows-phone-7-lg-e900/

Good luck!

Localised Resources for Silverlight Toolkit Nov 2010

PeterFoot — Wed, 19 Jan 2011 15:23:12 GMT

Due to the absence of a built-in DatePicker control many are using the Silverlight Toolkit which has a Silverlight implementation to match the control used in the native applications. One limitation in the current release is that the UI is only available in English. The day/month names are retrieved based on the device locale but the page header and text labels for buttons are always in English. I had a look at the code to implement a fix, interestingly I found that the strings were already stored in resource files, it’s just that there were no resources for other languages. I’ve submitted a set of .resx files to cover all the currently supported Windows Phone 7 languages so hopefully my patch will be integrated in a future release. I’ve also discovered that by creating my own localised resource dlls from the latest source I can use them against the current release binary. We are sharing these files for other developers who use these controls and write multi-language software for Windows Phone. To use these simply copy the contents of the ZIP file into the install folder for the November 2010 toolkit on your machine which will be somewhere similar to “C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.0\Toolkit\Nov10\Bin”. As a bonus these resources also localise the On/Off text on the ToggleButton control.

If you’ve not attempted building a localised application before have a look at this article on MSDN - http://msdn.microsoft.com/en-us/library/ff637520(v=VS.92).aspx. Mostly this involves standard RESX editing but for Windows Phone you have to make a minor edit to your project file with a text editor, hopefully this can be fixed in a Visual Studio Patch/Service Pack.

Download AppaMundi.Phone.Controls.Toolkit.Nov10.Resources.zip

LG E900 Review

PeterFoot — Mon, 17 Jan 2011 16:21:26 GMT

I have had a fair bit experience with the test devices which were available prior to the release of Windows Phone 7 but this is my first experience with a commercial device. Therefore it seems inappropriate for me to try and compare this device with other hardware or even to look at the WP7 OS itself as I’m sure you are already familiar with the standard features. Instead I’ve looked at the hardware under real day-to-day usage and had a look at features which LG has added to the phone.

Hardware

The device measures 12.5cm tall by 6cm wide and is about 12mm thick. The hardware buttons and arrangement are pretty standard. The row of buttons below the screen for Back, Start and Search are very tactile and give good feedback in use rather than some devices where buttons are built into the glass of the screen. The Start button specifically is a raised Windows logo which makes it very easy to navigate by touch if for example you are worried about walking into a fountain while using it (http://www.youtube.com/watch?v=mg11glsBW4Y&feature=player_embedded).

The back cover is dark lacquered metal and the sides are plastic and are easy to grip. Connectivity is provided via a micro-USB port on the right-hand side and there is a headphone socket on the top of the device and a wired headset is included.

Screen

The screen is 3.8 inches, very bright and clear indoors and quite usable outdoors too. I’ve recently tried the Kindle reader application on the device and found it quite comfortable for a few short reading sessions.

Camera

The camera is marked as 5.0 mega-pixels. For a phone the results were quite good but don’t be under the impression that this is comparable with a similarly spec’d digital camera. I’ve found myself more inclined to use the camera for quick shots now that WP7 has a shortcut to launch the camera from a locked state using the hardware button. The device has a small mirror on the back to help you take a self-portrait if you so wish and an LED flash which can be turned on or off or used automatically. LG have implemented custom settings in the form of “Photo Smart Settings” accessible from the Camera app which allows you to change between a number of 4:3 or 16:9 widescreen resolutions and adjust the brightness and white balance settings. There is also a link to Panorama Shot which is a cool utility to help you stitch up to 5 images together into a panorama. It gives you a live overlay on the screen to show you where to position the camera for the next shot. The results were quite impressive and because you have the finished panorama on the phone you can upload it to Facebook or SkyDrive or send in an email using the Pictures hub.

Battery Life

I’m not a heavy user or Wi-Fi or cellular data most of the time, as such I found I only had to charge the phone every other day. Turning off Wi-Fi and Bluetooth most of the time keeps battery usage to a minimum. Perhaps I’m unnaturally frugal based on my experiences with other phones so your experience may differ.

LG Applications

The device ships with some LG specific applications. Tiles are installed on the Start screen for three of these – ScanSearch, PlayTo and Panorama Shot.

The app I was particularly interested in trying was PlayTo which allows you to output to a DLNA compliant screen. We have a TV with DLNA support but have never really taken advantage of it. When you first run the app it will search for a compatible device. It soon found our TV and connection worked. The TV may have additional settings or a process to ask for permission when you connect a new device. We then have the option of playing Music, Pictures or Videos. I tested a few tracks of music from my device. I have a mixture of MP3 and WMA files and I found the TV refused to play the WMA files but worked okay with MP3. The track name and album art were also transferred which I wasn’t expected and it looked impressive, you can use the controls on the phone to skip tracks as well. Photos worked well with a couple of galleries including photos taken on the device. You can browse a carousel of images on the device and select them to be sent to the TV. Videos were not so successful. First I tried playing a video clip captured on the device and it would not play. I suspect this is because the TV doesn’t support the codec used but it is a shame. I would assume that being able to show videos you have captured would be the main use for this functionality. I guess this is a limitation with DLNA devices at the moment.

ScanSearch is an augmented-reality application which searches for a number of categories of places in the local area (restaurants, banks etc) and overlays them on screen over the live camera view based upon the compass in the device. Personally I’d prefer to see results on a map but having the map turn as you turn the device would be quite clever. This is obviously an OEM specific feature as regular developers have no access to the compass and can only read the Course from the GPS data which will only be accurate when you are moving.

Alongside the pre-installed applications there is a special area within the Marketplace for LG specific applications. There they make available a number of other apps for free (often for a limited period) from system utilities to a golf caddy.

Issues Encountered

The device shipped was customised for Vodafone Germany and so it had some features specific to that network. Also it showed a feature that OEMs are able to add an additional accent colour which in the case of Vodafone is their corporate red.

Because the device was built for the German market the initial boot occurs in German but it can be changed to any of the other currently supported languages – English (US or UK), French, Italian and Spanish. I found that when set to English a number of third-party applications which support multiple languages in the Tile and Application Name were showing a name in German. I don’t know if this is an issue with Vodafone Germany’s customisations or something in WP7 itself…

Wi-Fi has been somewhat unreliable for me. When it connects it’s great but after a while it will fail to reconnect and only restarting the wireless hub and the device can get it to reconnect. I have seen this with other devices so I suspect it is my wireless hub rather than the phone which is to blame.

Conclusion

This has been a great day-to-day device, it has a good sized screen and is slim. I found the battery lasted long enough for my usage. I like the fact that devices are standardising on the micro-USB port so I can carry a few different devices and one USB charger. I found the intermittent Wi-Fi issues annoying but I suspect my wireless hub is at fault so will investigate changing it. The LG specific features such as PlayTo and Panorama Shot are valuable additions to the OS and well integrated.