The XNA/GS 3.0 CTP is out and I'm in the process of updating the VBContentManager in preparation for the official release.
XNA 3.0 content processing expects to use the .NET Framework v3.5 edition of MSBuild. For those not interested or ready to move to XNA 3.0, XNA 2.0 compatibility will be retained in the VBContentManager.
To that end, the GS 3.0 release will mark a small change in how the VBContentManager works. A version enumeration is now required by the VBContentManager class, and moving forward, the VBContentManager will be augmented with new version support (rather than replaced wholesale) so that future editions of the VBContentManager can target prior XNA versions (dating back to 2.0). Just pass in which XNA version you're targeting, and it will process your content accordingly.
The VBContentManager currently available for download was never updated with functional, XACT-based audio importing. I do have this working in my "production" VBContentManager, and as part of the 3.0 update I will include this for backward compatibility with 2.0's XACT-based audio. And of course the new audio importing for 3.0 will be available as well, which is what I'm working on now.
![]() | 5/10/08 |
Subscribe to:
Post Comments (Atom)

4 comments:
Hi, plan to update your template to 3.0? Or heard of anyone else doing a vb template for 3.0 ?
I haven't heard of any other projects targeted at vb & xna 3.0 specifically, so I'm not sure if there's anything out there yet.
But I am planning to release a 3.0 template; I'm about 50% done with a new content builder application which I intend to include with it. It does depend on my work schedule how often I get to work on it, so it may take perhaps another week if nothing horrible happens.
Nice. I have fubbled around in C# now but since Im working in VB and java at work, Im not to keen on getting a new language in the head at the same time :)
Appriciate your work by the way.
How much functional loss is there when using VB instead of C# for XNA? Not counting Zune or XB360 devs that is.
Atari ... those were the days...
The primary functionality loss in forsaking C# is Game Studio. Game Studio upgrades Visual Studio (or, Visual Express) to be "XNA aware", but only for C# projects. C# gets IDE features like starting new game projects and having Visual Studio understand the need to compile content prior to running the game. My template is effectively a crude band-aid over this loss :)
Apart from the Game Studio component, XNA itself is just another .NET library; when you're actually writing code, VB is on equal footing with C#, just like with a Windows application or whatever else.
And of course, there's the compact framework issues... that one stinks. Although I do reserve a 10-15% suspicion that it might be technically possible... I think if you could replace enough of the VB Runtime stuff with your own "pure" .NET wrapper, you *might* be able to get it to work, but... that's really going down the rabbit hole, and I don't even have an Xbox360 to test with :P
Post a Comment