c# application encountering a problem and closing for no apparent reason. Possible problems with 3rd party dlls -


We are building a C # application that will sit in the PC trash truck. Things work fine on our development machines, but like always, when we work on our target hardware then problems start.

One of the specially giving us headache. At random intervals, we will lift the message box of a window and say that there is a problem in our application and it needs to be closed.

The app still works fine, while the dialog box is sitting there, and obviously it closes when you click on the Close button. The disappointing thing is that we do not get any exceptions, nothing in any log, nothing in the system activity log. I have a queue that there is a problem in a third party library that we use for GPS There is a pure cover for unmanaged DLL which we already have problems. What do we have to try and debug ?? I am relatively new to Windows programming and am wondering if there are programs, we can use to know that the part of which DLL portion is being called by our code.

Cheers Nimai

I think these things are very difficult to debug, When this may be the problem only in third party native DLL

In the meantime you can load your app directly into your dynamic app loaded app domain instead of What can you do to make your app a little stronger than the way DLL will not bring a bus app domain down to your full AI If necessary, you can do some code (app domain) to start over again. Note that this is not fixing your problem, but at least makes the app a bit stronger in the field.

Note that there are some hoops to leap in accordance with marshaling data between your app domain, but nothing serious.

Edit: This provides a sample


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -