I am studying for an MCSD exam so learning to program in C#. Here's
the problem. The book I have wants me to add a component (separate
from the main form) and then put a timer on that component. I was
able to do that in my 60 day evaluation version Microsoft Visual
Studio .NET 2003, but this version has somehow crashed after I
installed some Server 2003 updates and I have thrown away the CD.

So I installed the free Visual Studio Express C#, but this doesn't
offer the choice to add a component. You are probably saying I should
just add a class. But here is the problem. I can't get the timer to
be in the same scope as the class it is supposed to act on, because I
can only drop the timer on the main Form instead of creating a
component for my DoghnutMachien class and dropping the timer in
there.

I am studying for an MCSD exam so learning to program in C#. Here's
the problem. The book I have wants me to add a component (separate
from the main form) and then put a timer on that component. I was
able to do that in my 60 day evaluation version Microsoft Visual
Studio .NET 2003, but this version has somehow crashed after I
installed some Server 2003 updates and I have thrown away the CD.

So I installed the free Visual Studio Express C#, but this doesn't
offer the choice to add a component. You are probably saying I should
just add a class. But here is the problem. I can't get the timer to
be in the same scope as the class it is supposed to act on, because I
can only drop the timer on the main Form instead of creating a
component for my DoghnutMachien class and dropping the timer in
there.

Hi,

i'm trying to set the serial port.(XP SP2, Visual Studio 2005). I use
the example code from MSDN "configuring a communications resource".

CreateFile pass through, however GetCommState return 0.With
GetLastError(), i get the error number 87, which means
"ERROR_INVALID_PARAMETER The parameter is incorrect. "
I'm sure the serial port works, because i can use another program to
read/write through it.

thx
Cheng

I managed to shrink the problem back to essentially an MFC Hello world, with
only a null keyboard handler to manifest the problem. Then, purely as a
guess, I removed one of the arguments from the handler, ie. changed the
prototype to ...(UINT, UINT), and the problem went away. I'm confused, all
the documentation I have on CDC::OnChar, the prototype is at the end. But
that standard form causes a crash.

It seems that these internal handler functions aren't type checked by the
compiler, I was able to set the args so that hte application was obviously
beset with a major problem (which was difficult to find) and there were no
errors reported. Is there some technique or settings that enable this sort
of nasty problem to be flagged? Or is this just something that the MFC
structure can't see?

Hi All,

Does anybody know why InterlockedExchange is implemented as

mov ecx,[esp+4]
mov edx,[esp+8]
mov eax,[ecx]
@retry:
lock cmpxchg [ecx],edx
jne @retry
ret 8

Instead of simply
mov ecx,[esp+4]
mov eax,[esp+8]
xchg [ecx], eax
ret 8

?

xchg automatically assets LOCK# signal and is atomic. What to make loops
for?

Oleh Derevenko