Xna3.1 -> Xna 4.0 Solving missing types

So i had 158 errors and the most obvious one was the mising definitions for certain types like..
Vector2
Vector3
Vector4
Rectangle

To solve this issue i created a brand spanking new Solution and opened it up. As the problem appeared to be mising references i started by opening up the referecnes for the new project, then comparing them with the ones in my broken project. Immediatly i saw i was missing a couple of very important reference files.
Microsoft.Xna.Framework
System.Net
Obviously without these there is no way it can compile. You can just right click the References line and say 'Add Reference' then simply browse for these two to add them in.

Onto the next issues later..
Oh, i have about 28 errors left, Yay!

Wow has accounted for my last night or two

I do have to say that it seems like an easy choice to play Cataclysm instead of developing games. Though this would not normally be true, IF in fact i could develop my game. However with Berzerkatron being stuck being upgraded to 4.0 Xna, it is hard to get into at all.

So instead of slogging through error  after error, i play Wow with my Son and our friends. Easy choice right now.

G'night

Dang Saving and Multiple devices

It seems that MS have half written the Saving code for the Xna suite. I would love to of just said i wanna save this file, and it handle it by noticing there are multiple choices and sorting it all out for me. Then keeping which device they chose etc internal to their system.

However they did not do this, so we all (all XBlig devs) have to go and do it ourselves. All of us writing very similar code to handle this situation. then we have to handle issues like the MU being pulled etc. The Xna community of Peers would love to be able to fail for not re-requesting confirmation if somone slects no device. It does get a bit more ocmplex than that but..

Take it from me, this is just not fun code to write. I have actually been there in the trenches on the PS2 and written all that crappy memory cardflow that they demand in their TRCs. If the user has swapped cards put up this message, then if he has a full card put up this one and then go around once more for the memory card dance.

Although i am complaining about MS in this case, it is not a fully heartfelt complaint. Their system is in fact a bit there, unlike the hell of the PS2.

Personally i couldn't care less if some bozo happens to pull out his MU while selecting the MU device. It seems to me he was in fact trying to break it anyway. BOO to you!

But i am not in a situation to ignore this current thread of making our games more robust for the BOZO's out there. Now i love good solid software, i do not like confirmations tbh. I write them into my code, but i do not really agree with a lot of them. The industry has just come to expect them, and maybe games players have to. To me i just am not sure where it should all end ?

Quit ?
Are you sure ?
Are you really sure ?
etc etc.. i know ya get my meaning here.

Well back to the main reason for this post. I cannot find a nice flow diagram of what i need to write to make the MU and hard drive selecting work in a nice manner. One that has confirmations in it, and handles errors and the like. Therefore i need to create one. haha!

Yup i love me some diagrams at times. This one i will vet through the XBlig and Xna community first to see if i can get a good consensus on what we all want. Then i can get on and write it once, not more than once which i also hate, lol.

g'night