If your goal is to learn all about the internals of Windoze, then you need
to master the SDK.  If you just want to crank out some useful GUI programs,
then the learning curve is lower, but still pretty steep with MFC, which
covers up some of the more glaring internal inconsistencies of Windoze with
a more-or-less consistent collection of objects.

Again, if you're just wanting to crank out a useful program or two,
Borland's C++ Builder has an even lower learning barrier, and is still able
to produce fairly compact programs that don't depend on dozens of dll's that
are never the right version, like with Visual Basic.

I have a setup program I wrote for a PIC-based product, which takes user
data via a nice dialog box, and sends that to the PIC via a serial
connection.  It is a completely standalone .exe that needs NO .dll's and is
under 300K.  It took a few days to figure out the Borland tools, but that
was sooooo much less than the several months it took me to figure out VC++
and MFC...

> -----Original Message-----
> From: John Waters [SMTP:john_fm_waters@HOTMAIL.COM]
> Sent: Friday, December 03, 1999 1:51 PM
> To:   PICLIST@MITVMA.MIT.EDU
> Subject:      [OT] win32 SDK  versus  MFC
>
> Hi All,
>
> I need to develop some C programs in MS Visual C++, I can either use the
> simple MFC or the more flexible win32 SDK utilities as the key development
> tool. Before I start, I want to make sure I've made the right choice since
> I
> don't want to come back half way in the future.
>
> Could anyone give some suggestions or make a comparison between the two?
>
> Thanks in advance.
> John
>
>
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com