Debugging on a machine one doesn't have access to

[Robert W.]

I have a prospective client who can't get my WinForms app running on his
machine. I sent him some sample .Net apps and they run fine. The error
coming up is very cryptic and doesn't help me resolve the problem.

My "traditional" way of debugging like this would be to create a special
version of the software that would simply write out designated milestones in
the app, like "1", "2", "3", etc. This info and maybe a little more
peripheral text would get written into a text file. Using this method I
could narrow down where the app was crashing.

But I'm thinking that .Net may have a superior way to resolve such a
situation. Does anyone know of one?

--
Robert W.
Vancouver, BC
www.mwtech.com

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

What error are you getting?

Can you post the text of the exception?

Send him a debug version (and send the .dbp too ) , make sure you are
intercepting all the exceptions ( AppDomain.UnHandledException,
Application.ThreadException ) and create a log with them.
log both the Message and the StackTrace , also make sure you check
Exception.InnerException.

--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Robert W." <Ro*****@discussions.microsoft.com> wrote in message
news:B8**********************************@microsof t.com...

I have a prospective client who can't get my WinForms app running on his
machine. I sent him some sample .Net apps and they run fine. The error
coming up is very cryptic and doesn't help me resolve the problem.

My "traditional" way of debugging like this would be to create a special
version of the software that would simply write out designated milestones
in
the app, like "1", "2", "3", etc. This info and maybe a little more
peripheral text would get written into a text file. Using this method I
could narrow down where the app was crashing.

But I'm thinking that .Net may have a superior way to resolve such a
situation. Does anyone know of one?

--
Robert W.
Vancouver, BC
www.mwtech.com

[Robert W.]

Ignacio,

The error msg he's getting reads:

Application has generated an exception that could not be handled.

Process id=0x980 (2432), Thread id=0x710 (1808)
Could you expand upon what you said: "make sure you are creating a log"? Is
there a special way to do this with .Net or just as I described earlier?

--
Robert W.
Vancouver, BC
www.mwtech.com

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,

What error are you getting?

Can you post the text of the exception?

Send him a debug version (and send the .dbp too ) , make sure you are
intercepting all the exceptions ( AppDomain.UnHandledException,
Application.ThreadException ) and create a log with them.
log both the Message and the StackTrace , also make sure you check
Exception.InnerException.

--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Robert W." <Ro*****@discussions.microsoft.com> wrote in message
news:B8**********************************@microsof t.com...

I have a prospective client who can't get my WinForms app running on his
machine. I sent him some sample .Net apps and they run fine. The error
coming up is very cryptic and doesn't help me resolve the problem.

My "traditional" way of debugging like this would be to create a special
version of the software that would simply write out designated milestones
in
the app, like "1", "2", "3", etc. This info and maybe a little more
peripheral text would get written into a text file. Using this method I
could narrow down where the app was crashing.

But I'm thinking that .Net may have a superior way to resolve such a
situation. Does anyone know of one?

--
Robert W.
Vancouver, BC
www.mwtech.com

[Robert W.]

Ignacio,

Is this the kind of custom exception handling you were thinking of:
http://www.c-sharpcorner.com/Code/20...onHandling.asp

--
Robert W.
Vancouver, BC
www.mwtech.com

"Robert W." wrote:

Ignacio,

The error msg he's getting reads:

Application has generated an exception that could not be handled.

Process id=0x980 (2432), Thread id=0x710 (1808)
Could you expand upon what you said: "make sure you are creating a log"? Is
there a special way to do this with .Net or just as I described earlier?

--
Robert W.
Vancouver, BC
www.mwtech.com

"Ignacio Machin ( .NET/ C# MVP )" wrote:

Hi,

What error are you getting?

Can you post the text of the exception?

Send him a debug version (and send the .dbp too ) , make sure you are
intercepting all the exceptions ( AppDomain.UnHandledException,
Application.ThreadException ) and create a log with them.
log both the Message and the StackTrace , also make sure you check
Exception.InnerException.

--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Robert W." <Ro*****@discussions.microsoft.com> wrote in message
news:B8**********************************@microsof t.com...

I have a prospective client who can't get my WinForms app running on his
machine. I sent him some sample .Net apps and they run fine. The error
coming up is very cryptic and doesn't help me resolve the problem.

My "traditional" way of debugging like this would be to create a special
version of the software that would simply write out designated milestones
in
the app, like "1", "2", "3", etc. This info and maybe a little more
peripheral text would get written into a text file. Using this method I
could narrow down where the app was crashing.

But I'm thinking that .Net may have a superior way to resolve such a
situation. Does anyone know of one?

--
Robert W.
Vancouver, BC
www.mwtech.com

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

"Robert W." <Ro*****@discussions.microsoft.com> wrote in message
news:60**********************************@microsof t.com...

Ignacio,

The error msg he's getting reads:

Application has generated an exception that could not be handled.

Process id=0x980 (2432), Thread id=0x710 (1808)
This message says nothing, you need to see the Exception.Message &
Exception.StackTrace.
Try to run the app from a prompt, not double clicking it in win Explorer.

Could you expand upon what you said: "make sure you are creating a log"?
Is
there a special way to do this with .Net or just as I described earlier?

Just create a file to log any exception info. You could also use a
EventLogger
Remember to use the debug version along with the dbp

--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation