thread differences from button_click and timer_elapsed (winForms - interop)

Hi, I'm experiencing some kind of thread behavior problem in a WinForms app
in Vb.Net 2.0.

Actually I'm doing some huge interop using DirectShow to interact with my
miniDV camera.

The problem is that if I put the code to read the camera's timecode inside a
button_click routine it works just fine, but, if I put that code to run on a
timer_elapsed event I get error (in particular, NotImplementedException from
the interop layer).

The question is: what is different in calling a method in a button click
routine and in a timer elapsed event (in threads meaning) for the interop
layer, is that the "user
interaction" (button click) that creates a new thread automatically or sth
like that?


Thanks for any clue,
Victor

Found that... just change the system.timers.timer to forms.timer to run all
operations on the same thread.



"Victor Reboucas" <vcreb (AT) hotmail (DOT) com> wrote

Hi, I'm experiencing some kind of thread behavior problem in a WinForms
app
in Vb.Net 2.0.

Actually I'm doing some huge interop using DirectShow to interact with my
miniDV camera.

The problem is that if I put the code to read the camera's timecode inside
a
button_click routine it works just fine, but, if I put that code to run on
a
timer_elapsed event I get error (in particular, NotImplementedException
from
the interop layer).

The question is: what is different in calling a method in a button click
routine and in a timer elapsed event (in threads meaning) for the interop
layer, is that the "user
interaction" (button click) that creates a new thread automatically or sth
like that?


Thanks for any clue,
Victor