Are you saying to skip MFC altogehter and learn the Win32 API? Is this how it is "usually" done?
Feedback from you or anyone else is appreciated :)
Printable View
Are you saying to skip MFC altogehter and learn the Win32 API? Is this how it is "usually" done?
Feedback from you or anyone else is appreciated :)
Yeah my advice is to first learn it the API way before going MFC... But I think when you want to go .NET, choose C#, because this is the language especially written for .NET
Hmm okay I will learn the API. Any suggestions on where to start? Books, tutorials etc?
I've used the Win32 API many times in the past for VB, so im not a total newbie!
The API isn't that hard at all with some MSDN and platform SDK..
for a good Win32 tutorial: http://www.winprog.org/tutorial
Thanks for the help! :)
Read this for arguments for the API and against MFC, and it gives a good view on why :)
http://winprog.org/tutorial/apivsmfc.html
This article is very good (IMO, partly because it supports my point of view). I think the most important part is in the last paragraph and defines the time when you're ready to try out MFC:
When you know enough API that you can translate solutions given to you in API to MFC.
Hi Cornedbee, mind posting that link again? That thing you posted up is just undelined text! :)
and *bump* for the Americans who've had a long weekend.
That's not a link. It's something picked from the link in the post above mine.
Ahh lol, yes, im sorry, ill take a look. Thank you.