Some of you are using the name C# as though it's a GUI API, I think you mean Windows Forms for C#.
Some of you are using the name C# as though it's a GUI API, I think you mean Windows Forms for C#.
Details, details.Originally Posted by indigo0086
Anyway, how many GUI APIs there are for C# anyway?
"The Internet treats censorship as damage and routes around it." - John Gilmore
Well there's...
*Takes vase and runs away*
>Anyway, how many GUI APIs there are for C# anyway?
Two, if you only count the ".NET" frameworks: Windows Forms and Windows Presentation Foundation. You can also hook into the Win32 API and other third party libraries if you really want to.
My best code is written with the delete key.
Hammer's are better than screwdrivers!
Personally I dislike C# and will probably never use it, but that is because it does not meet my needs. Is it C+=2? no, definately not. But I see that it might be Microsofts attempt to get scripters away from Visual Basic and into a more flexible language. If all your job entails is writing gui interfaces for simple applications, then C# may be the way to go if you do not already know win32. Its probably easier to learn for most new users. Even Microsoft admits that for Raw Horsepower you need C/C++, just look at the Express downlaod page and how it describes each package.
My job entails a lot of HPC and custom hardware interface's. I need the low level control and flexibility that C/C++ provides, so C# isn't even an option of last resort for me. Other programer's may have different needs though, so C# may be a better choice for them.
Last edited by abachler; 03-31-2008 at 11:14 AM.
