Well, although not a perfect match, here are the C# versions of MFC concepts
MainFrame: Form (that would be the main Form)
Doc/view: The wizard doesn't do this for you but you can always have this
architecture if you want.
Dialog resource file: You have everything written out to the
"InitializeComponent" method of the Form that's being designed.
CString: string
Notify Messages: You're right. They come as events.
Worker/UI threads: You set the "IsBackgroundThread" to true for worker and
false for UI (well, that's the general usage, although there's not a whole
lot of difference between the two; Background threads don't keep a process
alive without atleast one foreground thread)
ANSI/Unicode: You set the Encoding. Look up System.Text namespace
Timer: Timer. Windows Forms has a Timer component that you can add to any
Control.
Since you have plenty of experience in MFC, the samples in MSDN and the
Tutorials should be good enough to get you started off with C#.
Good luck!
-vJ
"Scott" <ba*********@hotmail.com> wrote in message
news:77**************************@posting.google.c om...
I have written windows applications using MFC for several years and
have frequently used MFC techniques.
Now I'm moving to C# .NET WinForm. Mostly C# books describes C#
language (sometimes compared with C++) and then how to use Windows
Forms but without comparison with MFC.
Would you recommend any book or online stuff to guide migration from
MFC/Win32 to Windows Forms to save time and effort to learn new
environment. I realized that it is next to impossible to map
mechanically. At this time all I need conceptual migration or hints.
Examples I need are as follows (Right hand side answer could be
incorrct, because I'm a newbie)
MFC => .Net Windows Forms
MainFrame => ???
DOC/VIEW architecture => Nothing. Just dialog
Dialog resource file => Hard coded in C# file
CString => ???
Notify Message => Event...
Worker/UI thread => ???
ANSI/Unicode => ???
Timer => ???