This error means your assembly doesn't contain the information that identifies which XNA Framework runtime is required to run your game. XNA Game Studio 2.0 and onward embeds this information in every game assembly you build. Since we didn't embed that information in XNA Game Studio 1.0/1.0 Refresh, the error message makes the assumption that the game must have been built with a version prior to 2.0.

If your game is not written in C#, then you are obviously not using XNA Game Studio -- and that's why you're missing this information from your assembly.

To get the missing data into your assembly, follow these steps:

1. Create an XNA Game Studio game project for the platform that matches your game.
2. Build that project.
3. Open Explorer and browse to the intermediate output directory of the project you built (eg, obj\Xbox 360\Debug).
4. Observe the file called Microsoft.Xna.Framework.RuntimeProfile.txt.
5. Now open the non-Game Studio project you used to build your game.
6. Add the Microsoft.Xna.Framework.RuntimeProfile.txt file to your game's project.
7. Set the item's Build Action property to Embedded Resource.
8. Close the project.
9. Open the project's MSBuild project file (.vbproj?) in the code editor (it's XML).
10. Find the <EmbeddedResource> element that includes the .txt file, and add the following child element:

    <LogicalName>Microsoft.Xna.Framework.RuntimeProfile</LogicalName>

Now your project is set up to embed the information used by xnapack.exe.

The runtime profile is a token that identifies the runtime requirements of the assembly. It maps to a specific version of the XNA Framework - so they are different for Zune, Xbox 360, Windows, as well as different for CTP, Beta, and final releases.

When you use XNA Game Studio, we manage this information for you so that the project and the tools work correctly together, and you are given appropriate error messages when you try to mix and match incompatible assemblies. However, when you don't use XNA Game Studio to build your games, you can't expect the rest of the tools to work for you, either. This is part of what we mean when we say that we only support C#.

 Am I missing something else?

Initially, I missed that you were using v2.0. In v2.0, we only had one runtime token for both Windows and Xbox 360 -- which is a mistake we have remedied in our subsequent releases. So for a CCGAME created with v2.0 XnaPack, the runtime token is expected to be "v2.0" as you inquire.

Getting this to work properly will depend on how well you understand MSBuild and your project's MSBuild integration.

Since you are using a compiler that I'm not familiar with, I can't say exactly what you need to do to embed the resource correctly. In a VB or C# MSBuild-based project, the Microsoft.Common.targets file is imported to do most of the work. According to these targets, if a LogicalName is specified, it is used as the name of the manifest resource - otherwise, one is assigned based on the project's default namespace, the location of the item, and the item's name.

If you build a default Windows Game project, you'll see in the Output Window that the runtime profile is specified on the C# compiler command-line like this:

 (Sorry, not sure why that pasted so small, or why I can't change the size after the fact...)

If your compiler supports specifying the logical name of the resource, then you need to set up your project to specify it, according to your product documentation.

Sorry I can't be of any more help - embedding resources is a compiler-specific action, and even if it's available, the MSBuild project might not support providing a non-default name. You'll need to check your product documentation or ask the vendor.

 One last question... Is the line

/resource:obj\x86\Debug\WindowsGame6.obj.x86.Debug.Microsoft.Xna.Framework.RuntimeProfile.txt,Microsoft.Xna.Framework.RuntimeProfile

 <Import Project="$(MSBuildExtensionsPath)\Microsoft\XNA Game Studio\v2.0\Microsoft.Xna.GameStudio.Common.targets" /> directive?

Or by the C# compiler?

Thanks again for all your help.

CartBlanche:

One last question... Is the line

/resource:obj\x86\Debug\WindowsGame6.obj.x86.Debug.Microsoft.Xna.Framework.RuntimeProfile.txt,Microsoft.Xna.Framework.RuntimeProfile

generated by

 <Import Project="$(MSBuildExtensionsPath)\Microsoft\XNA Game Studio\v2.0\Microsoft.Xna.GameStudio.Common.targets" /> directive?

Or by the C# compiler?

Neither.

The Game Studio targets only generate the TXT file and add it to the list of embedded resources, along with the logical name. The MSBuild targets that process EmbeddedResource items are in Microsoft.Common.targets, which is installed with the .NET Framework. In a C# project, most of the work is done by Microsoft.Common.targets, but eventually a number of computed values are passed to targets in Microsoft.CSharp.targets (also installed by the .NET Framework).

The list of resources to embed is passed to the CSC task, which constructs the command-line. The command-line is then passed to the C# compiler.

So really Game Studio does not do anything special, except to add the TXT file to your project without having it appear in the Solution Explorer. If you followed the steps I described previously in a normal C# project, you'd get the exact same result as building a Game Studio project.

The C# compiler doesn't generate the command-line because the C# compiler doesn't run until it is given the command-line to execute.