Skip to main content

Windows Phone 7: Detect device type

The Windows Phone 7 Emulator is a great way to test your applications before deploying them. However there are obvious limitations, such as working against the GPS system where the emulator just can’t quite cut it. In those situations it is common to create some sort of simulation to mimic the desired behavior.

But once you have deployed your application to a real device you do not want your simulation routines to execute. Fortunately you can check for the DeviceType and avoid calling any emulator specific code you may have embedded.

Checking For the WP7 Device Type

The System.Devices.Environment.DeviceType property returns either DeviceType.Device or DeviceType.Emulator indicating what platform the application is running. Notice that reading the Microsoft.Devices.Environment.DeviceType property generates garbage, causing garbage collections when you don't want them.  Therefore it’s better to call it once at the start of your app and save the value.

Here is a simple example how you can do this:

   1:  public class Settings
   2:     {
   3:         public static Settings Instance = new Settings();
   4:   
   5:         private Settings()
   6:         {
   7:             IsRunningInEmulator = CheckIfRunningInEmulator();
   8:         }
   9:   
  10:         public bool IsRunningInEmulator { get; private set; }
  11:   
  12:         private bool CheckIfRunningInEmulator()
  13:         {
  14:             return Microsoft.Devices.Environment.DeviceType == DeviceType.Emulator;
  15:         }
  16:     }
  17:   
  18:   

So instead of calling the DeviceType property each time you needed it you would call the IsEmulator property which would rely on the _isEmulator variable after the first call.

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more