For a number of years the software development industry has struggled to find a solution to a rather old idea: write once, run everywhere. First, there was Java, which for a little while seemed to be the answer, however for numerous reasons it didn’t live up to the dream. For a while it looked like everyone gave in, and the chase was off, however Microsoft released the .NET Framework and the game was on, once again.
A recent IDC forecast of shipments of tablets and smartphones predicts that by 2017 87% of connected device sales will be tablets and smartphones. More specifically the forecast predicts that 5-inch devices will take the lead, followed by 7 and 9-inch tablets. Computer sales meanwhile are slowing down and the sales forecast is not encouraging. These forecasts underscore the direction that enterprises should focus their efforts; that is invest in mobile development, connected devices and how to get most out of these investments.
This posts is motivated by my personal struggle fixing PCL (Portable Class Libraries) project support in latest version of Xamarin Studio (4.2.1 stable). I’ve been working for a while on a iOS project where some of the core components are built in a PCL project. Before the Xamarin Studio version 4.2.1 a hack was required in order to be able to correctly build and use PCL projects in iOS solutions using Xamarin Studio.