Rampid Byter

I started reading the Beginning .Net Game Programming in C# book recently as part of what I’ll describe as a robot-information gathering session. I’m trying to learn as much as possible on game AI that will help me in understanding how to program a robot that is able to understand its environment. I will say that I’ve gotten about two chapters into this book, and I’ve already started to form the opinion that while the author has an understanding of the material they’re cocky pricks. Here is an excert from a paragraph from chapter 1:

“If you think this is too much math, this is probably the place where you should take this book back and take up something less mathematically demanding, like nuclear physics! Honestly, we can’t overemphasize how important math is when it comes to computer games. . . . “

I suppose before getting into the BEGINNING book you’re already supposed to have a firm grasp of all the algebra, and geometry involved in game programming. OH, that’s right I’m just trying to learn what is involved to start the learning process. So maybe they’re right, maybe you should take this book back, and have the author(s) shove their opinions up their arses. I could then have someone who caters to beginning learning give me a better, less condescending introduction. Pricks. At least if you can overlook the snarky attitude that is probably oozing in the remaining chapters the book seems to be decent thus far. I plan to skim the rest of the way through this book before the end of the month so I’ll post some more thoughts and opinions later on. I may even post some code from the game.

I’m currently at work learning the nuances of the PHP language for an upcoming project. I was thinking about a way to start off the one sided conversation we’ll be having from now on, and then it hit me. I’d like to take a moment to help you solve a problem that plagued our development team for three days with RDLC reports.

Just recently I was attending a Microsoft MSDN event, and of all places while I was waiting at the line for the concession stand I overheard a group of three developers complaining about RDLC implementations, and Infragistics control sets. Having just rolled off a four month project where RDLC reports were part of my primary development tasks I learned quite a bit. I won’t touch on the Infragistics controls just yet as the pain of dealing with them is still very fresh within my thoughts.

The most important thing that I learned during this period of time is that deploying/publishing a website with RDLC reports is a big pain in the butt. What you’ll realize is after you’ve compiled and deployed your site the RDLC files drop from the 30+KB file sizes to a 1KB size. This change alone can throw some developers for a loop, but fear not this is normal. Unfortunately most of you out there that deploy these reports will be exposed right away to this wonderfully descript error:

“The definition of the report ‘Main Report’ is invalid”

Having stared blankly at this error, and considering we had no reports definitions named ‘Main Report’ this threw us for a loop. Looking up possible solutions to this error through Google amounted to a heap of nothing. There were forums after forums making off the wall suggestions to correct the problem, and even a few MSDN forums with advice that amounted to adding three .dll files to the GAC (global assembly cache) on the deployed server.

It wasn’t until we found this very obscure site that mentioned that by default the .Net framework does not include the ReportViewer control. In order to display reports correctly you’d need to additionally locate, download, and install the ReportViewer software on the website server. For our development systems this was never an issue as Visual Studio (VS) installs the ReportViewer once installed, but for our VS-less web hosting server this became an issue.

At the time of writing this blog entry you can find a reference to this Report Viewer control from the Microsoft download link below:

Microsoft Report Viewer Redistributable 2005 

Additionally you can search on the Microsoft.com website for the Microsoft Report Viewer Redistributable 2005 software. This will correct the ‘Main Report’ error, and hopefully at this point the reports will be displaying correctly. I’ve seen a lot of suggestions, everything from replacing the compiled versions of the RDLC reports with their source versions to including additional files into the GAC. The underling cause of this problem is most servers do not have Visual Studio (VS) installed, and without VS the report viewer control is not installed by default. Anyways, I hope you enjoyed my first blog, and I look forward to talking at you later.