I am working on a casual game on XNA with a view to deploying it on the Xbox 360. I will not have access to the equipment for several weeks, and I am in a short time, so I would check for example that several things - Boo and several user libraries - will work correctly on 360. If they do not, I need to get around them sooner rather than later, so testing is very important.
This explains why there is a way so that I can go to the "simulator" to run the code on the .NET Compact Framework for 360, before actually deploying to 360?
Well, you can try to write a quick application for a Windows smartphone and run it in an emulator. Obviously, this will not work for specific XNA code; but for any runtime libraries that Boo or what you use, work on the emulator, they should work on the Xbox.
For the XNA code you write yourself, just compile it for the purpose of the Xbox 360.
As TraumaPony said. Just load the main assembly of the game in Visual Studio and try to compile it. This will not happen if you try to make a link to the assembly outside those that come with 360.
, 360, . , . , , , . , , : -)
, , Xbox 360 .Net, , , .Net. , , , Xbox , , , . , , 360, .
, , , , . , Boo XNA, , .