WPF Application Errors and .Net Framework Repairs

Question

Background: I have a .Net 3.5 WPF \"Prism\"-based application running on Windows XP and Windows PosReady 2009 PCs. The app runs on PCs that are shut down every

Answer 1

Have you tried remote debugging the production system?

What you need to remote debug are:

• deploy msvcmon.exe
• network connection between your development and production system
• make sure your local and remote version of the code are in sync. You can also build on your dev machine, and xcopy deploy your debug build to the remote machine. If it's pure .net code that is the easy. If you also have C++ code you should make sure the debug versions of the C++ dlls are on the production machine. Or, build the release version and remote debug that.
• setup a user account used for the connection. This is actually a bit tricky. Google remote debugging credentials for a few tips.
• don't forget to disable all firewalls!

You can attach to an already running process, but you can also start the app from inside visual studio.

If your development system is located far away from the production system, use a laptop and remote desktop to bring your developer studio to the production system. I do this routinely. Even a five metre distance between the two is annoying.

I can elaborate on this, if there's interest, or if you run in to trouble setting up the connection.

Good luck!