in

This site is all about the amazingly cool stuff you can do with VB.NET.

The VB.NET XNA Project

XNA GS 2.0(beta) deployment platform bug (what causes it and how to workaround it)

First... how to cause the problem.

1. Create a new C# Windows Game 2.0 project in VS2005.

If you take a look at this point, in the Configuration Manager, you will see 2 entries. One is for the Content project and the other is for whatever you named your new project. So far, so good.

2. Add a new VB.NET Class Library project to your solution. (Make sure to add it to the solution, not create a new one.)

Take a look in the Configuration Manager again. Now you'll see 3 entries, including a new one for the VB.NET Class Library you just added. You should also notice that the Content project's Platform has changed from x86 to Xbox 360. That's a problem.

Fortunately, fixing it is easy enough.

3. Click on the Active Solution Platform dropdown box and select x86 (it probably says Mixed Platforms when you look at it.)

4. Save, Recompile, etc...  you're all set.

FWIW, this has already been reported to Connect (you're welcome) and has been marked as fixed in the final version. After all, we are using Beta stuff, so it's not entirely unexpected.

 

 

Comments

 

Blogus Maximus said:

XNA GS 2.0(beta) deployment platform bug (what causes it and how to work around it)

November 28, 2007 1:57 PM

About admin

Chris Williams is a Technology Evangelist for Magenic. He is the founder of several .NET User Groups on the east coast, and most recently the Twin Cities XNA User Group (www.twincitiesxnausergroup.com) in Minneapolis, MN. He is a VB.NET MVP, rabid blogger and owner of www.ILoveVB.NET. He's also a MCT, MCSD (.NET) Early Adopter, MCAD, freelance game developer, occasional author, tech editor, code camp & user group speaker, vintage arcade game collector and plays a pretty mean guitar in Rock Band.
Copyright 2008 - ILoveVB.NET
Powered by Community Server (Commercial Edition), by Telligent Systems