Search code examples
.netwinapijobs

Sphere of application of WinAPI


I'm a starter C and C# programmer, mainly developing for the Windows platform (XP and above). My programs are quite small tools with GUI, so I'm currently using WinAPI for writing them. I like WinAPI for giving me almost full control over my programs, and I spend a lot of time on learning it. I asked myself if my knowledge of WinAPI is worth my time spent on learning it (I mean, if I'll be able to use this knowledge later as I'm a future developer), but I couldn't find an answer.

I would use .NET Framework, but then Windows XP users will be forced to install huge .NET Framework package just for running some small tools. I don't really like that.

So, are there still are some areas where WinAPI is at least good way to go? Would it be better not to spend my time on learning it now and stick with .NET?


Solution

  • First of all, let me ask you a question:

    Why do you think that you need full control of everything when coding GUI apps? I do not see the point? Windows users expects GUI applications to look as windows GUI applications. No need to have full control then.

    imho there are no justifications to do everything yourself instead of using an existing framework like MFC or .Net. You can still get control if you like, but for most of the time you don't have to.

    Best of all: You can do everything in a fraction of the time compared to doing everything by yourself.