Alright, this problem is driving me insane. I'm using C# and managed DirectX and 2 out of the 3 people I've given my demo to have had the same weird problem. The second they try to run the program, they get a box that says "application has generated an exception that could not be handled". The program runs fine on my computer and my friend's computer and everything DirectX related is in try/catch statements. I googled and got a mess of people with driver and .NET security access problems that I already ruled out, so I figured I'd post here to see if anyone knows what this is about. I would go more in depth about the code of my application but the funny thing is, the people that can't run my application get the exaxt same error with the DirectX SDK samples for C# that I compiled. I already made sure they had the latest versions of .NET framework and DirectX. Has anyone had this problem and figured out the solution to it? Is there something really simple that I'm missing about developing with DirectX and C# then distributing the files? Another thing that may be note worthy is that my friend that could run the program has the DirectX SDK and C# .NET installed on his computer. Please, any help would be apreciated, I'm running out of options here and my project will die if half the people on the team can't run the demos.

Unfortunately my test subjects have all gone to sleep now, but I'll try giving them the managedDX.cab in the morning. If it works, I owe you my life :)

ok, I have confirmed that the problem was that they simply needed to install the mdxredist.msi (found in the managedDX.cab) that for whatever stupid reason is NOT included in the standard DiretX 9.0c but is essential for anyone to run a managed DirectX program.

Microsoft rate--
thoue rate++

People can install the Managed DirectX stuff using the standard DirectX redist.
they need to add a command-line to their directX installation :
/InstallManagedDX

So you dont need to send them that msi (its in the redist, just not intalled by default).

But the MDX stuff IS in the standard directX redist - so everyone is getting it. You just have to specifically say you want to install it ( .NET is a prereq and not as many have that ).

Once .NET becomes more prevalent, they might make it automatically include the already included MDX component.

At the moment however, it is generally easier to ship the MSI with yoru software than to ask people to re-run their DirectX installer with a commandline (easier in the sense that it can be automated).