Fortsätt till huvudinnehåll

A mobile app using Xamarin

Today I started on a mobile app for my common-law wife. She is starting a workout program and I thought I could code up a simple Android app that she can use to keep track of the different exercises and the number of repetitions or duration to do them for.

As I have been working with C# for couple of years now and I feel comfortable with it I thought I would try using Xamarin. I discussed the functionality for the first version with my partner and sketched up a simple model of the entities. Then I figured it would be a good idea to try out a simple tutorial to get a feeling for it and ensure I have all the needed tools installed.

In the Visual Studio Installer there is a check box for mobile app development so I checked that and let everything install. Then in Visual Studio I created a new Android project, built it and pressed F5 to see what would happen.

No go! The Android emulator wants virtualization to be enabled in order to run in hardware accelerated mode. So I had to reboot the computer and turn on virtualization in the BIOS settings for my computer. Ok, attempt number 2.

Failure once again! This time the emulator refused to start complaining that it couldn't find proper x86 support. After fiddling around with it a bit I realized that it was possible to start the emulator from within powershell, using the exact same command line that Visual Studio attempted. And if I pressed F5 inside Visual Studio while I had the emulator already running Visual Studio nicely connected to it and loaded the app.

By now the time for one evening of coding had ran out. I did however post a bug report on Visual Studio explaining that I am unable to start a debug session towards the Android emulator from within Visual Studio without starting the emulator manually first.

Next time I hope to get some actual code written!

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

C# Enum as bit field

Bit field enum Whenever you wish to express combinations of properties of an object, bit fields are a good way to accomplish this. As a simple example, consider a file in the file system. It can be Readable , Writable , Hidden or a combination these. The different attributes can be defined as an enum : [Flags] public enum FileAttribute {   None      = 0b0000;   Readable  = 0b0001;   Writeable = 0b0010;   Hidden    = 0b0100; } To indicate that this enum is expected to be used as a bit field I have defined it with the FlagsAttribute . It is important to understand that the FlagsAttribute does nothing more than making some changes to how the ToString method of the enum works, making it possible to print out all flags. It does not introduce any validation or special treatment of the enum in any other way. I have defined the values of the different fields of the enum using binary representation, this should make it even more clear that this is a bit field and which bi
Skicka en kommentar
Läs mer

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i
7 kommentarer
Läs mer