Welcome to Omgili,
Omgili ( Oh My God I Love It ;) is a search engine for discussions. With Omgili you can find answers and solutions, debates, discussions, personal experiences, opinions and more... To learn more about Omgili click here.
This is a complete preview of the discussion as it was indexed by Omgili crawlers. Use this preview if the original discussion is unavailable.
Click here to view the original discussion.
 |
|
 |
|
XXX.exe has encountered a problem and needs to close.
I've been using Visual Studio 2008 Express C# with the XNA framework to code, and everytime I run my program, I get an error window saying that "XXX.exe has encountered a problem and needs to close.
We are sorry for the inconvenience," where XXX.exe is the project I'm working on.
This holds true for all programs I've created, from a simple empty window popping up to the beginnings of a game.
The error window is always on top of everything, and when I close it, my program closes, so it's hard to work around it.
Initially, a JIT debugger window popped up, and I looked for a solution to that.
I found two solutions, neither of which worked.
The first was to change my DEP settings so that it was only on for essential windows functions, but this was already the setting that was on.
The second solution was to enable Dr.
Watson, which is how it went from the JIT debugger to the "Send error message to Microsoft?" style window.
After neither of these worked, I uninstalled all programs relating to visual studio, then reinstalled those that I still needed.
This also did not work.
I've searched the internet for other solutions, but the ones I tried seem to be the only ones that people are offering, so I hoped to find another answer here.
Any help you can give would be greatly appreciated.
|
|
 |
|
 |
|
|
|
|
Windows 7 will be out soon, you definitely ought to consider installing it.
|
|
|
|
|
|
|
|
|
Hi,
If this is on a different machine to the development machine - (ie.
A Test Machine), try the following:
1.
.Net Frameworks (It does not always complain and request them - and sometimes just produces an error)
2.
The correct DirectX as per the development environment or greater is installed.
Ie. If developped on Dx9, youll need Dc9+ on the client.
3.
Try remote debugging, or 'bind' your debug session to the 'process' or running .exe
4.
Avoid "try catch" statements that just chuck away the errors without handling them...
Atleast log them in a text file or something, if you need to hide them from the user...
|
|
|
|
|
|
|
|