I have a VS2012 solution and WPF application, runs without exception in release and debug mode, but if I try to profile it the application crashes when I perform some UI actions (opening VMs, their view controls etc...)
Is there anyway to debug the exception when the application is ran in profiling mode?
You can always attach debugger to proces. Just open Debug->Attach to proces. If you want to break on any exception just press Ctrl+Alt+E and select proper option. If exception happen not in your code you could try to load pdb for selected dll.
No. There's not a lot of reason for an app to fail only when it is being profiled. It is usually something simple, like the working directory being different so your app will fall over when it does something unwise like trying to open a file with a relative path name. And no try/catch to handle the missing file problem.
What you need to focus on is what will happen when your app runs on the user's machine and crashes like this. Without a profiler but the very same problem of not knowing why it crashed. You'll need to spend a bit of time writing code that reports unhandled exceptions. Write an event handler for the AppDomain.CurrentDomain.UnhandledException event. Log or display the value of e.ExceptionObject.ToString(). Now you've got a good exception message and the Holy Stack Trace that shows you exactly how your program ended up crashing. Almost always good enough to figure out a small change in your code to prevent the crash. Or a better way to help the user's IT staff to fix the problem.
