Windows Programming -- WIN32 API Versus C#

[Guest_imported]

I am developing an application where normally(prior to .Net) I would have developed it using the WIN32 API and C. I have read a bit about C# and it seems like it may have a place in the world of application development, but most of the sources I have found seem a bit biased.

Would anybody recommend using C# to develop an application over C/WIN32? My main concerns are that .Net is a little beefy, it seems to me that it adds another layer to speed up development at the expense of speedy execution.

Thank You
scott

 

[ColinM]

Maybe you could write unmanaged code for any speed critical sections?

 

[chiph]

rapid-scott -

I've done Win32 windowing code in the past, starting with Windows 3.0. I skipped over all the MFC stuff, as I never really liked it, using VB instead. After taking a look at .NET and C#, I really really like it, and I'll be making the switch.

So far as performance concerns, I wouldn't worry. After all, you aren't going to be putting any performance-intensive code in the windowing code anyway, right? You'd do that stuff (db access, network access, computation, etc) in another thread. Besides, with the fast machines we have nowadays, most CPUs are idle, even when painting window contents.

Chip H.

 

[sjc]

If I was starting off a new application I would never start writing it in C/C++ and MFC. Sure you have experience, tried and tested methods etc and they do count for a lot but small learning curve from C++ to C# will allow you to jump in at the deep end in C# development. This will give you the wealth of classes that enable true RAD and being supported by .NET IMHO is almost like being led by the hand through the dev process. Some people will hate that and want to get as low down as possible but for the majority, they just want to write stable code and get it out asap.

Your concerns about speed are of course valid whenever another layer is introduced but I think only time will tell how effective the platform is for various app types. Don't compare the run time with Java's as they are quite different in execution and I think Microsoft (for once in my opinion) have got it right.
.NET will be big as the idea behind it is a good one (Even M$'s competitors agree on that) so don't be saddled with the long term support of a huge unwieldy MFC app that will keep you tied to it for x years, when you and the rest of the world will want to be doing .NET stuff.

 

[Guest_imported]

The .Net framework is fast enough to code huge biz. solutions. And if you learn how to use whats all in there, it realy pays off. So dont stare questioning yourself if you want to use it.. TRY IT.. you will be sold, I promiss.
C-Sharp is very unlike other languages, but java is prob. the most look a like if you study the code... Well its not, it's much much nicer to write.

If you are in need of a good RAD language and the platform of the customer may have .Net framework installed, I can advice anyone to go for the C-sharp development language.
In terms of development speed, it will help you solve those impossible deadlines. and in terms of beatifull code, It is even more sexier than Java...
The components delivered with the .Net framework, are really nice.. Databinding for your 3 tier apps, works out quite well. For 3D engineering, C++ is still the way to go, cause DirectX support is not that great at the moment. But every bigger application that needs a front-end and a Database, or a Internet Communication Aplication it can be nicely written in the .Net Frameworks. I just finished my killer application for my company. And the respect has gone into the right direction... (as wel as my paycheck)

Greets