So as I blogged a few days ago about the issues I was having with getting to grips with all the issues I was having (which you can read here) it appears I’m getting to grips with all the added complexities of working on cross platform .NET based solutions. There have been some incredibly late nights involved, surviving on 5 hours sleep a night for nearly a week has taken it’s toll I can assure you.
If you look at the other posting on the site of late, chiefly the Windows 8 post, you’ll see that despite all the Profile hacking I did I still wasn’t happy (neither was ReSharper but that’s another story). I did end up migrating away from Windows 7 onto the Windows 8.1 Pro platform.
I’m a simple developer at heart. Although I love all the neat tricks of .NET and using advanced interface based abstractions and Mvvm I still like to stick to first principles – simple is always better. I didn’t like the fact that when I was dealing with lots of other peoples code and libraries my basic setup around Windows 7 wasn’t dealing with it properly or reliably. Most of the things you’ll find yourself looking at deal in some way with a profile that the Windows 7 OS isn’t compatible with. Profiles that target Windows 8 or Windows Phone 8.1 just don’t like it. You can’t even installed the required SDKs Windows 7.
So, I have moved on. I loved Windows 7, it served me very, very well. Was rock solid for me and I had a complex machine with an even more complex Windows configuration and until the last couple of weeks it motored on and munched through all my work.
Anyway, if you’re thinking of getting started with mobile development and Xamarin and you’re on Windows 7, upgrade. It’s as simple as that. You’ll save yourself lots of hacking around, late nights and stress when things go odd, and from what I can tell they almost certainly will.
So as I blogged a few days ago about the issues I was having with getting to grips with all the issues I was having (which you can read here) it appears I’m getting to grips with all the added complexities of working on cross platform .NET based solutions. There have been some incredibly late nights involved, surviving on 5 hours sleep a night for nearly a week has taken it’s toll I can assure you.
If you look at the other posting on the site of late, chiefly the Windows 8 post, you’ll see that despite all the Profile hacking I did I still wasn’t happy (neither was ReSharper but that’s another story). I did end up migrating away from Windows 7 onto the Windows 8.1 Pro platform.
I’m a simple developer at heart. Although I love all the neat tricks of .NET and using advanced interface based abstractions and Mvvm I still like to stick to first principles – simple is always better. I didn’t like the fact that when I was dealing with lots of other peoples code and libraries my basic setup around Windows 7 wasn’t dealing with it properly or reliably. Most of the things you’ll find yourself looking at deal in some way with a profile that the Windows 7 OS isn’t compatible with. Profiles that target Windows 8 or Windows Phone 8.1 just don’t like it. You can’t even installed the required SDKs Windows 7.
So, I have moved on. I loved Windows 7, it served me very, very well. Was rock solid for me and I had a complex machine with an even more complex Windows configuration and until the last couple of weeks it motored on and munched through all my work.
Anyway, if you’re thinking of getting started with mobile development and Xamarin and you’re on Windows 7, upgrade. It’s as simple as that. You’ll save yourself lots of hacking around, late nights and stress when things go odd, and from what I can tell they almost certainly will.