VB Crazyness

So I found out something interesting today while working in VB. Even though Debug and Release modes are no different since VB does not generate .obj intermediate files, there is an issue that sometimes the complier will not be able to generate good errors with a simple build command.

Today I had some funky errors stating that I had syntax errors where none existed, and error underlining on the line above where it was saying the error was located. Really strange stuff. I finally thought to do a rebuild (since there are no intermediate files - or so I thought, didn't think it would help) Apparently, this fixed my problem. Very strange....

If VB Modes Debug and Release are different, someone please feel free to comment on this and correct me as I would like to know the difference. C++ is obvious as they generate two separate assemblies that are very different due to the debugging information.

Updates

I have been working on my 2D engine of late, and I have been making some updates to the managers I have written tutorials on. I have already updated the GUI manager with regards to an issue I ran into with sprite tinting. I will also be updating it later to include the optimizations that I made last month using reference passing for some of the larger objects.

As far as the development of the engine, I have been making great progress on how I am going to handle the states of the game. This is greatly important for RPG style games where dialog changes, controls change, and GUI Components rendering changes based on the current location and activity in the game. I have written a state manager that takes much of this into account and I believe that it is quite an elegant solution. I will be posting a tutorial on this here later.

Check out the changes to the GUI Manager tutorials if you have used this code anywhere. It will save you a lot of headache when trying to tint sprites and you can't figure out why (I think I spent a good hour looking at it wondering why it wasn't working).