Re: BackgroundWorker in different OS
- From: "Patrice" <http://www.chez.com/scribe/>
- Date: Mon, 26 May 2008 14:08:48 +0200
This was just to check that if an error happens inside this function, you
have some kind of report rather than nothing produced....
It is really really weird that a function could be called or not depending
on the OS language which would make me really think the real souirce is
another problem.
Similarly and just for testing one of my moves would be to to call the
GenerateDefautlReport on the main thread...
My goal for now is not to correct the problem but to make things simpler to
find out what could go wrong...
--
Patrice
"antarikshv" <antarikshv@xxxxxxxxx> a écrit dans le message de groupe de
discussion :
24b76ae6-08c9-4e35-b7ee-4343d5a06a5b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
My guess would be rather that you have something that fails inside
this method preventing to see the result this method is supposed to
produce
and making things looks as if it were not called.
I had written MessageBox::Show as the first statement to be executed
in the called function, but the function wasnt called. So i am pretty
sure the control does not go to the function. I have even debugged the
code. The solution i found was just by luck. Solution is to just
recompile on English machine.
What if you intentioanly raise an exception in your code. Is it seen onWhat kind of exception should i raise? What benefit will be possible
your
English dev machine or does it fail silently ?
with this exception raising? (I mean which all points should be
monitored while these exceptions are being raised?)
.
- Follow-Ups:
- Re: BackgroundWorker in different OS
- From: antarikshv
- Re: BackgroundWorker in different OS
- References:
- BackgroundWorker in different OS
- From: antarikshv
- Re: BackgroundWorker in different OS
- From: Patrice
- Re: BackgroundWorker in different OS
- From: antarikshv
- BackgroundWorker in different OS
- Prev by Date: Re: BackgroundWorker in different OS
- Next by Date: Re: .NET still a problem - need better understanding
- Previous by thread: Re: BackgroundWorker in different OS
- Next by thread: Re: BackgroundWorker in different OS
- Index(es):
Relevant Pages
|