Back to the basics: win32 programming
-
In San Antonio, there were VERY FEW jobs available for anything other than DBAs. Of the jobs that weren't DBA, most were for C++ with a smattering of Java, and nothing for .NET. That was in May/June of 2004. My current job requires C++ with heavy MFC knowledge. They're still debating whether or not they'll even move to VC7, and there has been absolutely no discussion of going to managed code, C#, or .NET. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
I just got a .Net job in Austin and when I was looking it was about an even mix between C++/MFC, C#, and Java. But the corporate stuff was almost all either .Net or Java.
I can imagine the sinking feeling one would have after ordering my book, only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
-
It is not out to replace C++, it is just that many of us old time C++ people found that we can bend a little and reap huge levels of productivity Interesting, VB programmers have been saying that for over a decade. But, C++ programmers still insulted them regardless. But, now it's ok because C# has the letter "C" in it right? Jeremy Falcon
Jeremy Falcon wrote: But, now it's ok because C# has the letter "C" in it right? No, it's the curly brackets. ;)
Any remotely useful information on my blog will be removed immediately. Judah Himango
-
Jeremy Falcon wrote: But, now it's ok because C# has the letter "C" in it right? No, it's the curly brackets. ;)
Any remotely useful information on my blog will be removed immediately. Judah Himango
:-D Jeremy Falcon
-
Well you didn't say if it was a hobby or not, if it's a hobby do what you please, if you plan to feed a family for the forseable future, go directly to .net. Much of Win32 is UI related for obvious reasons and Microsoft seems lately to be hell bent on making that UI code obsolete. If this was 1988 I would recommend Win32, but I couldn't in any honesty give you one good reason to learn it now, it's starting to get pretty stale. If you want a career maintaining someone else's code that was written circa 1990 to 2002 for the rest of your life by all means learn win32, no responsible company is going to use it to write anything beyond drivers in short order. In fact even ATI now requires .net to install their latest video drivers (for the utility programs). Your not going to get and easy answer to this question here, there is a huge bias for win32 and a huge bias against .net (or at least there has been up to a few months ago) so don't expect a truly "agnostic" answer. You will likely also get a lot of people who will advocate that you should learn win32 because it's "Important" to know that kind of thing even if you are programming in a higher level language. That argument has always been utter hogwash, if you have the time and are curious fine, if you want to make a living stick to knowing what you need to know first, a professional programmer can make an excellent living (and write professional grade code) knowing absolutely nothing about win32 internals. If it's for work then you might want to take a look at the jobs being offered that you might be going after some day and see what they require. In all honesty, the last time I looked I think there were far more Java jobs than anything else on offer for corporate work, but that might have changed lately.
[Message Deleted]
-
[Message Deleted]
Diederik van Houten wrote: You think Win32 knowledge is completely redundant when using .NET He is wrong. In this .NET book[^] a whole chapter (I believe it is the sample chapter that can be read on-line) is about advanced WinForms details, and it is all about Win32 message handling. I have yet to see a real-life .NET desktop project where there are no calls to Win32 API functions.
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
-
It is not out to replace C++, it is just that many of us old time C++ people found that we can bend a little and reap huge levels of productivity Interesting, VB programmers have been saying that for over a decade. But, C++ programmers still insulted them regardless. But, now it's ok because C# has the letter "C" in it right? Jeremy Falcon
Quit using those dirty four letter words "VeBe"! Whack yourself on the backside for even mentioning it :) Rocky <>< www.HintsAndTips.com - Now with "Recommendation" postings www.JokesTricksAndStuff.com www.MyQuickPoll.com - Now with Recent Poll List www.GotTheAnswerToSpam.com - Again :)
-
Just wrote a small service to monitor a serial port, analyze the results, and send status out via UDP using Win32. I selected Win32 for its advantages in size and speed.
By projects, I didn't mean small stuff like this. The topic at hand was using Win32 to provide a GUI, over MFC, or at least I thought it was. I am sure the advantages you speak of exist, but I doubt they would be noticable over an MFC app on any remotely modern machine. Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
-
Quit using those dirty four letter words "VeBe"! Whack yourself on the backside for even mentioning it :) Rocky <>< www.HintsAndTips.com - Now with "Recommendation" postings www.JokesTricksAndStuff.com www.MyQuickPoll.com - Now with Recent Poll List www.GotTheAnswerToSpam.com - Again :)
I am ashamed. :) Jeremy Falcon
-
By projects, I didn't mean small stuff like this. The topic at hand was using Win32 to provide a GUI, over MFC, or at least I thought it was. I am sure the advantages you speak of exist, but I doubt they would be noticable over an MFC app on any remotely modern machine. Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
MFC and .Net both have huge libraries that need to be somehow loaded, also MFC really does nothing useful with serial ports or UDP. If it was a small / medium sized app with a UI, I would use WTL. Has almost all of the functionality of MFC in a much smaller footprint.
-
MFC and .Net both have huge libraries that need to be somehow loaded, also MFC really does nothing useful with serial ports or UDP. If it was a small / medium sized app with a UI, I would use WTL. Has almost all of the functionality of MFC in a much smaller footprint.
I'm not arguing with any of these points, just saying that in this day and age, I doubt anyone will notice the difference :-) Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer
