I agree completely with the Delphi route. Though, it would be a complete rewrite of the libraries and the UI. I've been using Delphi for ages and love it. You can get quite a lot accomplished in a short amount of time - think old school drag and drop placement of components for all platforms. You'll obviously need a Mac to target iOS and macOS, but if you're targeting only Windows and Android, all you need is your Windows machine. If a total rewrite is an option, I'd highly recommend Delphi.

When you see that an update is available, just start the VS Installer before bed and allow it to do it's thing overnight. Seems easier than juggling VMs.

How about a Byte? Each one in a group is a Bit. If there are more than 8 in the group, it's a Word of Software Engineers, more than 16 is a DoubleWord (or DWord), more than 32 is a QuadWord (or QWord), etc.

No doubt the Surface Laptop is a good option. I've been able to get essentially all day use from the new Surface Book 2. Not playing games or watching the Lord of the Rings Extended Edition Trilogy, granted. But getting real development work done using Visual Studio along with Internet research and email. Plus this thing has to drive a 15" HiDPI display, a discrete GPU, and a quad-core i7. I'd say that is a huge accomplishment in battery tech by the Microsoft Surface team. Kelly.

I used a 2011 MacBook Pro with BootCamp and didn't really have any issues. I then upgraded to a 2013 MacBook Pro and used VMware Fusion to run Windows 7 and Visual Studio (then Windows 10 and VS). I will say that the move to HiDPI/Retina caused some issues, but I was able to get them resolved through different settings adjustments. However, over the course of several macOS releases, things change and it became too much of a hassle to keep things working well. I recently switched to the new Microsoft Surface Book 2 (used Surface Pro 3/4 some too) and have to say that it is hands-down the best laptop I have ever used. If you primarily develop software using Visual Studio, I'd recommend getting the Surface Book 2 (or even an upper-end Surface Laptop or Surface Pro). Keep the MacBook Air in order to compile Xamarin Forms apps for Mac or iOS. Return the MacBook Pro if you can. Not worth the hassle when such good hardware is available. Hope that helps... Kelly.

I really don't have much of an issue with anything you posted except the part about the iPhone always "just worked" and didn't give you a hard time moving Apps to the SD card. There has never been a version of the iPhone with an SD card to move Apps on to. And the same is true with the iPhone 6. At least your HTC has that capability, as do most other Android phones and now Windows Phones. If your worried about space on your new iPhone, you better get the 64GB version or the 128GB version, because you're locked into whatever size you pick. BTW: I currently have the iPhone 5 and previously had the 4S, and 4, and 3GS. But, I'm seriously considering "jumping ship" to the new Moto X or the new Nexus 6/X (whatever they decide to call it) this go around. Cheers.

I agree with John. We use it for both WinForms and WebForms development and it works great. It does have a descent learning curve, but most frameworks that do what this one does have a fairly steep learning curve. I would definitely recommend it if your project size is medium to large. You should certainly get the book(s) and follow the active forum while you come up to speed. I have looked into some of the other offerings, but none match CSLA.NET. Rockford Lhotka did an incredible amount of work to limit the amount of work that developers using the framework must do in order to get a scalable, n-tier system up and running. Kelly.