I were just setting up some “tracking” on a Windows Phone 7 application, using PreEmptive Solutions Dotfuscator, when I got some odd problem. First I just setup all up as I use to and deployed to the WP7 emulator. Application started and shutdown right away. Hmm, I tried again and again, same thing happened. I then looked closer at the “Build Output” window in Dotfuscator and saw this at the bottom:

“Warning: The strong named input assemblies (or assembly) {Assembly name and path here } were not resigned. You will need to sign these dotfuscated assemblies manually”

I could figure out that the reason why I needed to resign it, were because dotfuscator have had a look on it – I therefore needed to figure out how to avoid it to do so.

It turns out that you can exclude assemblies inside dotfuscator, just go to the “Input” tab, expand your .xap file until you find the assembly that gives you problems, right click it and pick “Exclude assembly from Package”.

Just a little help if anybody else ends up with this problem

- Enjoy!

Over the last few days I have been working on an online high score for the Windows Phone 7 game ‘plan bee’, which is done in XNA. (I guess this problem is also relevant for Silverlight applications). I had the service setup and all were good, data were flowing back and forth. To give the player a good experience when playing the game I of course started to test the game without internet connection, as this can happen on a mobile device like WP7

Then the game crashed right away and at first I just thought I forget to check for something and attached the debugger. The debugger showed me that an EndpointNotFound exception were thrown. I tried a lot of things and couldn’t figure out how I could avoid or catch this exception!

More...

Some days ago I discovered this very promising platform for game developers.

“What is ExEn?
Currently ExEn is an implementation of a subset of the Microsoft XNA Framework API that runs on iPhone and Silverlight. It is based on XnaTouch and SilverSprite – but most of the important bits have been rewritten – most importantly the rendering, audio, input and timing systems.”

More...

Yesterday we – RambukGames - announced a little Windows Phone 7 game, plan bee, which we have been working on for some time now.

This is what we have been talking about on twitter for the last couple of weeks!

More...

Really, this doesn’t only apply to your designer, but to anybody other than the developers coding the game. Let me explain the problem we had in RambukGames and how we solved it.

More...