Author Topic: Upgrade wizard in Visual Studio 2005 and Visual Basic 2008 Express Edition  (Read 13310 times)

valcansa

  • Newbie
  • *
  • Posts: 1
    • View Profile

  • Total Badges: 0
    Badges: (View All)
I'm attempting to learn how to write some game programs using Visual Studio 2005 and or Visual Basic 2008 Express Edition.  I have found VB code of games that I figured would assist me in learning how to write.  However, when I open the project file, it goes through the upgrade wizard and when it does it encounters significant error messages.  I'm wondering if it's something I'm doing incorrectly?

Any assistance would be greatly appreciated.

Thank you

golem

  • Newbie
  • *
  • Posts: 13
    • View Profile

  • Total Badges: 0
    Badges: (View All)
Shocking isn't it?
« Reply #1 on: June 12, 2008, 04:46:03 pm »
:lol:

Sorry, not making fun of your problem... It's just the Microsoft way! ;)

What you are experiencing is what those MS pinheads consider normal.

Chances are you probably got ahold of some of the earlier VB.NET code and both the 2005 & 2008 IDEs will AUTOMATICALLY attempt to update the code to handle sweeping/significant changes in each environment.

The problem Valcansa, is that the 'upgrade Wizard' is the biggest POS ever concieved, was written by wannabe MS geniuses who never really used VB, it was AND STILL is a hatchet job that allows MS to claim they provided 'a tool' to 'facilitate' conversion between VB5/VB6/early VB.NET and the current version.

The bottom line, is you will want to go ahead and open the projects in your target IDE and tackle the conversion problems one by one.

A good place to start is to click (ctrl-click ;) ) on each of the warnings with the links for the 'exceptions'. You have about a 50-50 chance of getting help with that specific error. You will want to remain flexible in your thinking and exercise extreme patience... Cuz that is what it will take.

And TRUST ME, when I tell you the answers/fixes will often be counter-intuitive.

Another approach is to cut-n-paste the ID number into the search engine and it will take you to various .NET sites. I warn you that you are now down to 10-90 chance of getting any real help.

Most of the discussions will draw answers from guys that are supposed to be heavyweights, some with LOTS and LOTS of abbreviations like they are some kind of programming gods! saying things like "that's the old way" or my personal favorite... 'just rewrite the whole thing from scratch!'

The sad truth is they are mostly just gelding parrots who have ABSOLUTELY NO CLUE WTF you are talking about! :lol:

(I slay myself ;) )

But IF you persever, you WILL get an answer.

I am one clever devil and even SOLVED the GET/PUT of UDTs (VB5/VB6), using some rather unorthodox thinking... Just win baby... Just WIN.

The new models are SERIOUSLY convoluted (they shot RAD at dawn on the first day of the 'conversion' from VB6 to .NET! :) ), the 'thread safe' is a gas.

Chances are we've see it. ;)

So Valcansa... Just ask. :)