Note that there are some explanatory texts on larger screens.

plurals
  1. POProblems running XNA game on 64-bit Windows 7
    primarykey
    data
    text
    <p>I'm having problems getting my game engine to run on my brother's machine, which is running 64-bit Windows 7. I'm developing on 32-bit XP SP2.</p> <p>My app uses XNA, FMOD.NET, and another dll I wrote entirely in C#. Everything is targeted to x86, not AnyCPU. I've read that this is required for XNA to work because there is no 64-bit xna framework. I recompiled FMOD.NET as x86 as well and made sure to be using the 32-bit version of the native dll. So I don't see any problems there.</p> <p>However when he tries to run my app, it gives an error which is mysterious, but not unheard of.</p> <p>A <code>FileNotFoundException</code> with an empty file name, and the top of the stack trace is in my main form constructor. The message is <code>The specified module could not be found. (Exception from HRESULT: 0x8007007E)</code></p> <p>I found some threads online about this error, all with very vague, mixed, and fuzzy responses that don't really help me. Most remind people to target x86. Some say check that they have all the dlls necessary.</p> <p>I gave my brother <code>Microsoft.Xna.Framework.dll</code>, but does he need to install the entire XNA redistributable package? When I take everything I sent him and stick it in a random directory, it still runs fine for me. I developed the game in VS2008, <em>not</em> in game studio, using XNA 3.0 and a Windows Forms control that uses XNA drawing which I found in an msdn tutorial. I would also like to avoid requiring a full installer if possible.</p> <p>Any insight? Please?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload