Marcus Grenängen

Me and my co-worker Jevgeni Tsaikin will be doing the session "Skype for Windows Phone Does TDD" at DevSum 2013.

Join us as we walk you down our path towards Test-Driven Development. Over the last year, as we moved to adopt this approach, we overcame many obstacles, both technical and non-technical. In this session we are going to share the steps we took to making TDD our standard. We will dive into many technical details:

Visual Studio 2012 ships with a new Native C++ test framework. When writing tests and hitting a error message like this:
error C2338: Test writer must define specialization of ToString<const Q& q> for your class class
std::basic_string<wchar_t,struct std::char_traits<wchar_t>,class std::allocator<wchar_t> >
__cdecl Microsoft::VisualStudio::CppUnitTestFramework::ToString<SomeType>(const SomeType &).

With the release of Visual Studio 2012 and C# 4.5, [CallerMemberName] makes its entrance. With this new awesome feature you can write INotifyPropertyChanged code without having to worry about renaming properties and keeping strings in sync for the call to OnPropertyChanged(…).

As of a couple of weeks back, I'm a Software Development Engineer at Microsoft's Skype division working on Windows Phone.

If not, you should, and here is why, Canary tests is an internal test of your test setup and should be used when you have a complex setup method. The Canary is a internal test of your test setup.

A great example of when a Canary tests should be used, you have some sort of dependency injection with configuration files, and after refactoring you might have changed some names etc invalidating your wiring configuration.

Here is a quick example in C# using MSTest:

Microsoft and WP7 are still struggling with encodings other than en-US (US-ASCII). A great example of this is the BingMapsDirectionsTask found in the WP7 Mango API's.

Calling this task with a culture like Swedish where the decimal separator is a , (comma) character instead of a . (dot) character, will make it fail to parse latitude & longitude data. This is 2011, soon to be 2012, how can the WP7 team miss something so crucial and in my eyes, obvious use case.

I finally got my hands on the new HTC Titan device, it will mainly be used for developing apps. This brings us directly to the registration and payment process for Microsofts App Hub, it's required to be a paying member to be able to deploy applications to the App Hub and to be able to run & debug your applications from Visual Studio on your own device.

The experience for signing up and pay for the subscription is everything but good. Microsoft has major problems with the payment system. It won't process payments at all actually. And the number of affected people is overwhelming looking at the App Hub Community forums. And it seems to have been a problem for a long time. Why haven't it been fixed?

The ZeeYaa team is proud to have finished the first major release for iOS devices.

ZeeYaa for iOS was submitted to the App Store 31 October 2011, we're still waiting for the review process to start, stay tuned on http://zeeyaa.com for detailed information.
 
 

It will soon be released, and I'm already up N running 12.1 RC 1, it's performing well after some minor tweaks.

First of all, if your running a NVIDIA gfx card, you might have some issues booting you're machine, but that's easy to fix, in Grub, add the following as a boot flag:

nomodeset

After working around that, it's just a matter of adding it as a persistent option to Grub. The easiest way to do is to open YaST and go into boot, select your boot entry and add nomodeset at the end of the boot options.

This thing has really gotten out of hand. Forcing new users to sign up to Facebook to be able to use your service, WTF! Not only that, you have for way to long polluted my UI with Facebook crap and being social. You just lost a long time customer due to the fact that I DON'T WANT TO BE SOCIAL, and I don't want anything to do with Facebook.

It appears that I'm far from being the only one. We might not be as many as we would like, but hopefully it will burn a hole in you're income, Spotify.

Burn Spotify, Burn!

As some of you might have noticed, I've been involved in a start-up called ZeeYaa. We have today released the first BETA to a number of users.

This release is iOS specific for now, and a Android application is already under development, no one will be left out. Did someone say Windows Phone 7? Well, we'll write an application for that as well, as soon as Mango has been starting to roll out from OEM's on some actual hardware.

The new MacBook Air is great, but be sure to verify what SSD disk you got when you purchased it. Otherwise you might have been given an old and much slower Toshiba disk instead of the Samsung disk that is/was? supposed to be shipped with the new Air.

So why does this matter? Well, simply put, make sure to get what you're paying good money for. And you will actually notice the speed difference if you compare the two disks to each other, even with simple tasks such as unzipping a fairly large zip file.

OK, so Apple finally pushed the Lion seed as RTM, and yes, it's the same as the GM pushed to dev's a couple of weeks back. The MD5 is the same for the two files and it will most probably be marked as already installed in App Store if you've downloaded the GM release.

Well, yes. It's a sensational headline, but I can't find another way of putting it. Me and a colleague was pair programing, he's running Fedora witch is a great distro, but, it suffers from Gnome 3 and I had to suffer through two days of Gnome 3.

Gnome 3 in short, is a monstrosity that gets in your way all the time, really all the time, and to whomever is in charge for usability and design, please make a career change, cause you're a bad bad designer / interaction designer / usability expert or whatever you call yourself.

Well, a clean install of the Lion GM seed and the results is in. Looks good, seems much more stable and much needed settings for stuff such as Mission control and Launch pad has arrived in System Preferences.

Lion is right now actually usable, it doesn't crash as often as it did in some of the dev previews. Still no crash on different hardware (iMac 2011, MacBook PRO Late 2010).

A lot of my standard apps behaves a bit flaky, such as Firefox, but Mozilla and the other's will hopefully fix this before the actual release.