stand-alone

How does it not work? What happens when you run it?

Chris

Take a look at the way you load your resources (textures etc.). If you use relative path such as '..\..\media\texture.dds' the exe cannot work outside the bin/release or bin/debug or foo/bar folder.
Instead use a configuration file that is located in the same directory as your exe and contains the actual relative or absolute path to your resources.
This way you only need to modify this config file if you move your exe to another folder.

HTH,
Pat.

1) If your game is using C# and managed DirectX the end user has to have the .NET framework AND managed DirectX extensions installed.

2) Only give the .exe from the release folder to others.

3) Have a good way to handle relative paths.

I for example take the absolute (=complete) path to my exe file and build my resource file names from there. So i always build a complete path to load resources. Since i'm working from the path from the .exe i do not need any configuration, just the resource files relative to it.

4) If you need additional external libraries you need to deliver the accompanying dlls (or link them static).