Since early childhood we are taught that newer is better. The new toy outshines the old one. That new car is better than the one you just finished paying for. Etc, etc.
Of course I’m too smart to buy into that junk, right? Well, maybe not. I spent some time installing Visual Studio 2005 because it’s newer, better, shinier. Of course, I then had to set about to convert by game project which compiled and ran fine in Visual Studio 2003. This should be painless, right?
I know what you’re thinking right now. You’re thinking that I’m trying to lead you to believe that it was easy but instead it was really hard, right? Well, no.
It was actually really easy. I opened the project and 2 seconds later I was set. Or so I thought.
What VS can’t do is help you from yourself. Old libraries needed to be recompiled, and this meant the PopCap SexyFramework as well. While the project was converted admirably and compiled, tons and tons of compiler and linker warning were spewed. I should have paid attention to them, but I was eager to play with my new toy. Recompiling SlaughterFest V seemed to work fine… until I actually had to change the code. To make a long story short, I finally got everything to work perfectly, downloaded a VS 2005 friendly version of SexyFramework, and spent hours and hour just to get to parity!
Yay!
Well, it’s not all bad. The new IDE is actually rather nice and has a few features that have been sorely lacking in the previous releases, features that make my life easier, and that’s what it’s all about: spending an entire night wrestling with arcane errors to make my life easier…
On a related note, I haven’t worked on the SlaughterFest V since my last update on it maily due to work. Now, having reached the good place, I think I’ll be able to devote a few hours during the weekend to continue this project. I can’t wait.
I will now issue a challenge to myself. Self, I challenge you to update this blog by Sunday morning *with good news* about the status of the project.
Let’s see how things go.