"AMercer" wrote:

> How about StackTrace? That will do it unless you have multiple instances of
> the same form running.
>
> "Dom Sinclair" wrote:
>
> > Firstly my apologies if I have posted to the wrong group.
> >
> > Using visual Studio 2005 and programing in VB.net
> >
> > I have an application which, in the event of an unhandled exception, sends
> > an e mail back to me giving as much information as it can from the exception
> > message that was generated. Needless to say however it's not always
> > sufficient to clean a clear idea of what it is that went wrong so that I can
> > set about correcting it and release a patch to my end users.
> >
> > I'd like to know if there is a way to get information about the form that
> > was currently open at the time that a serious exception happens so that I
> > could narrow down the problem that much quicker and would welcome any
> > suggestions that any of you may have or indeed whether there is an entirely
> > better approach to this problem.
> >
> > The goal is to improve the end product for my customers, and having long
> > given up the pretence that I write perfect code first time every time I now
> > like to try and make it as easy as possible to diagnose problems in the field
> > and help my customers use the software in the way they want to use it. I
> > have discovered the hard way that relying on a customer to tell you exactly
> > what they were doing frequently fails to correspond with what they were
> > actually doing and it's as much of the latter that I would like to try and
> > get returned to me to assist in diagnostics.
> >
> > I must stress that I'm not after keystroke monitors or indeed anything as
> > intrusive as that just a little more precise information about which part of
> > the application was being used at the time an error occured.
> >
> > Many thanks for any thoughts that you may have, and should this be in the
> > wrong place would you be so kind as to direct me to the correct forum.
> > --