The C# 3 and .NET 3.5 Bandwagon
 | |  | |  | |  | |  | |  |
Introduction
Even though I consider the C# programming language, and for that matter the JAVA programming a waste of the C++
bandwidth there are practical reasons for a C++ developer to be proficient at C#. Those reason are:
This article addresses the needs of a C++ programmer writing C# .NET code. Unless explicitly stated so all statements,
classes, structures, function calls, function call parameters, behave exactly as they do in C++. The real distinction being the
modifiers on the parameters on the classes and structures. This article will point out the issues to watch for while writing C#
code.
C# has two type of objects, value type object and reference type objects. Value type objects exist on the stack and reference
type object exist on the heap.
Even though I consider the C# programming language, and for that matter the JAVA programming a waste of the C++
bandwidth there are practical reasons for a C++ developer to be proficient at C#. Those reason are:
- C# is well integrated into Microsoft .NET technology. Even though you can easily write .NET application with C++ the
Microsoft powers have not gone out of their way to make C++ feel well integrated into their set of .NET application
languages. - There seems to be lots more C# .NET work springing up and one does need for feed one self
This article addresses the needs of a C++ programmer writing C# .NET code. Unless explicitly stated so all statements,
classes, structures, function calls, function call parameters, behave exactly as they do in C++. The real distinction being the
modifiers on the parameters on the classes and structures. This article will point out the issues to watch for while writing C#
code.
C# has two type of objects, value type object and reference type objects. Value type objects exist on the stack and reference
type object exist on the heap.
