MFC is a great time-saver, and as long as yu don't step too far out of MFC's own (sometimes quirky) sense of reality, you should be fine. Any program that makes use of a pre-designed class framework is going to be larger than one which doesn't. MFC programs will grow if you include any of the following capabilities: - support for windows sockets - support for MFC collection classes - support for com/atl/activex - support for databases (odbc, ado, dao) Of course, you can compile your app using the MFC DLLs which makes your programs smaller at the expense of having to ship the MFC DLLs, as well as the possiblity that some rogue install program will overwrite those DLL's with an older version. I personally prefer to statically link MFC. Sure, it makes my apps a little larger, but I don't have to worry about those stupid DLLs either.