Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m a C# developer working with either Windows Forms or WPF. Sometimes I have to deal with unmanaged code, which I don’t like. I think that the main reason why I dislike this is ignorance. I don’t know the underlying Win API.
I think that I’m not the only person who has negative feelings against unmanaged Windows code.
Question: Should a Windows Forms\WPF developer start digging the WinAPI in order to be a better developer?
Sorry for not being very clear..
Thank you.
I think that looking at the WinAPI could be counter-productive to WPF, since it has a largely re-written stack. Even more so if you are looking at WPF in parallel to Silverlight.
It might be marginally useful occasionally for winforms – but I’ve been writing winforms for years, and have only once or twice needed lower level details. Every time I did, ‘google’ did the job fine; or more recently, stackoverflow ;-p
If you were writing raw windows directly, then maybe. But that would be unusual for C#.