Why C#

[AliR]

Hi All,

The question is why should I use C#?
If am developing a windows application, what are the advantages of using C#
versus VC++ (MFC)?
Thanks
AliR.

[Nicholas Paldino [.NET/C# MVP]]

In the end, it depends on the person. There will be some people that
find using MFC much easier than .NET. However, most people find that .NET
is about a gajillion times easier to use than MFC.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"AliR" <Al**@online.no spam> wrote in message
news:cG******** **********@news svr25.news.prod igy.net...

Hi All,

The question is why should I use C#?
If am developing a windows application, what are the advantages of using
C#
versus VC++ (MFC)?
Thanks
AliR.

[Brian C. Barnes]

I'm not going to get into a language war - use whatever fits your style and
the needs of your application - however, I will say that you will help
yourself if you dump MFC and switch to .NET - with either C# or C++ (or any
of the other languages available).

I used C++/MFC for many years. Then I switched to C#/.NET for personal
projects when that was available, because the C++ support for .NET was pretty
disappointing. Now, C++/.NET is a much more viable solution, and I am
thinking about switching back to C++ again (which is what I use at work all
the time).
"AliR" wrote:

Hi All,

The question is why should I use C#?
If am developing a windows application, what are the advantages of using C#
versus VC++ (MFC)?
Thanks
AliR.

[Mark Rae]

"AliR" <Al**@online.no spam> wrote in message
news:cG******** **********@news svr25.news.prod igy.net...

The question is why should I use C#?
If am developing a windows application, what are the advantages of using
C#
versus VC++ (MFC)?

That's very difficult to quantify. The "general" consensus of opinion is
that .NET is *MUCH* easier to use than MFC so, logically, you could expand
on that and say that easier to use means quicker to develop, and quicker to
develop means quicker to market, and quicker to market means faster return
on investment...wh ich can only be a good thing... :-)

However, only you can decide whether you find .NET easier (i.e. quicker)
than MFC...

[RobKinney1]

Hello AliR,

(usually I see you in the C++ sections!) Our company has decided to go with
C# for our new devlopment for a few reasons (we still use C++ on a ddaily
basis).

It just works. It makes more sense and you use a lot fewer lines of code to
do the same thing as in C++... Like with the TansparentStati c text... C#
already takes care of that automatically (your class saved my neck on a
deadline though for C++!).

The controls look a lot better.

Version control should be a lot better with the OneClick development
(compared to our current method).

Office automation (what a nightmare) is supposed to be easier and I have
been finding more documentation for it than with C++. ... Actually I have
found more examples with VB.NET which I think we can still incorperate in our
C# code (not sure how that works yet).

From what I have read there is supposed to be more consistancy accross OS's
using C# (or just .NET in general) since it is the same framework. I know we
have had problems in the past between differnt Windows versions with some of
the software we write in C++.

Sockets are supposed to be easier according to my comrade in the next room.
He said something about SSL being built in to the .NET framework whereas we
are having to use a 3rd party library for it in C++.

Alot of these things are just projections and things I have been told to be
true... and with the little programming I have done so far, a lot of it
checks out. I am not a pro though (entry level, small company). Pleaes
don't hold me responsible for these comments if they are in error... these
are the preconceptions I have about it from what I have read, etc... Can any
one confirm these comments?

Rob K
"AliR" wrote:

Hi All,

The question is why should I use C#?
If am developing a windows application, what are the advantages of using C#
versus VC++ (MFC)?
Thanks
AliR.

[Flip]

> If am developing a windows application, what are the advantages of using

C#

The main reason I moved from VB to java (bear with me for a sec. :>) was
cause it was closer to the OS, lower level power than VB, but not so low as
the C++ layer. I was rather disappointed with java though (just overall,
everything was rough around the edges). Then I started looking at C# and
found it VERY nice! Yes, it is easier IMHO, like others have said. But
what makes it easier?

First thing that comes to mind is NO MORE POINTERS!!!!!!! !! haha But the
truth be told, you still do have them, they're just called references. I
went to VB from C cause I hated pointers! Then after learning more and more
about java, they have pointers as well (like C#, just by another name,
references). So that was a bummer, but then you get over it and move onto
my next point. :>

The major thing that makes C# nice, easy to use, is it allows you to
concentrate on WHAT you're trying to do, not HOW. It's the WHAT that I love
so much! With Visual Studio (any version :>), you can simply draw your
form, double click controls, add handlers, etc. You're into the meat and
doing what you want to do. With C++ I find you spend sooooooo much time
setting things up, setting up the framework, getting the communications,
setting up classes, etc. IMHO, there's soooo much time wasted on the HOW,
by the time you get to the what, you're bored and don't care anymore.

But that's must IMHO. Good luck! :>

[AliR]

Hi Rob,

I am glad the Transparent Static class helped you out. :)

The reason I asked this question here is that, for the past year every time
I talk to a headhunter about jobs they tell me that they haven't ran into a
C++ job in a while, and all the companies that they deal with want C#
programmers.
I have read a book on C# (Teach yourself in 21 days, got it free from
codeguru for my Transparent Listbox), and I am reading the Wrox Beginner C#
..net 2005 now. What I have noticed so far is that it is easy to develop
simple dialog base applications (I don't deny that), but it seems very
difficult when it comes to MDI applications. Specially in regards to Docking
windows, menu/toolbar management. I also find it's event handling a bit
convoluted. It's just not easy to read, and know what events are being
handled and which ones aren't.

So the reason I asked this question here is that I wanted to know why people
prefer C# over C++. I don't have enough expirence with C# to make a good
judgment about the language, but from what I have seen so far I find MFC
easier to deal with, and alot more flexiable than C#. So I wanted to find
out from people who actually use C# what they find like about it.

AliR.
"RobKinney1 " <Ro********@dis cussions.micros oft.com> wrote in message
news:CD******** *************** ***********@mic rosoft.com...

Hello AliR,

(usually I see you in the C++ sections!) Our company has decided to go with C# for our new devlopment for a few reasons (we still use C++ on a ddaily
basis).

It just works. It makes more sense and you use a lot fewer lines of code to do the same thing as in C++... Like with the TansparentStati c text... C#
already takes care of that automatically (your class saved my neck on a
deadline though for C++!).

The controls look a lot better.

Version control should be a lot better with the OneClick development
(compared to our current method).

Office automation (what a nightmare) is supposed to be easier and I have
been finding more documentation for it than with C++. ... Actually I have
found more examples with VB.NET which I think we can still incorperate in our C# code (not sure how that works yet).

From what I have read there is supposed to be more consistancy accross OS's using C# (or just .NET in general) since it is the same framework. I know we have had problems in the past between differnt Windows versions with some of the software we write in C++.

Sockets are supposed to be easier according to my comrade in the next room. He said something about SSL being built in to the .NET framework whereas we are having to use a 3rd party library for it in C++.

Alot of these things are just projections and things I have been told to be true... and with the little programming I have done so far, a lot of it
checks out. I am not a pro though (entry level, small company). Pleaes
don't hold me responsible for these comments if they are in error... these
are the preconceptions I have about it from what I have read, etc... Can any one confirm these comments?

Rob K
"AliR" wrote:

Hi All,

The question is why should I use C#?
If am developing a windows application, what are the advantages of using C# versus VC++ (MFC)?
Thanks
AliR.

[Mark Rae]

"AliR" <Al**@online.no spam> wrote in message
news:fU******** **********@news svr11.news.prod igy.com...

What I have noticed so far is that it is easy to develop
simple dialog base applications (I don't deny that), but it seems very
difficult when it comes to MDI applications. Specially in regards to
Docking
windows, menu/toolbar management.
I can't compare C# with C++, but it's my experience that WinForms C# is
vastly superior to VB6 when it comes to MDI apps. I reckon I can develop an
MDI app in C# in approximately a third of the time it would take me in VB6.
I also find it's event handling a bit convoluted. It's just not easy to
read,
and know what events are being handled and which ones aren't.

Again, that's not my experience at all. I really like the C# events,
especially when used in conjunction with ASP.NET and all the event bubbling
that goes on there...

[Pete Davis]

I suspect that once you've done it for a while, you'll find that C# is
actually far easier than C++. Docking is pretty simple and I doubt MDI apps
are going to be all that difficult either, though in all honesty, I haven't
done an MDI app yet.

I did C++ for years and I liked it for the power it gave me. But I switched
to C# and after 3 years, I can't even imagine going back to C++. I've had to
for a few things and each time I've found it painful. Dealing with strings,
all the memory management (not that it's completely gone in C#, but it's
MUCH easier).

In C#, I can be 4 to 5 times as productive as in C++.

When it comes down to it, that's the only reason I need. It makes me far
more productive.

Pete

"AliR" <Al**@online.no spam> wrote in message
news:fU******** **********@news svr11.news.prod igy.com...

Hi Rob,

I am glad the Transparent Static class helped you out. :)

The reason I asked this question here is that, for the past year every
time
I talk to a headhunter about jobs they tell me that they haven't ran into
a
C++ job in a while, and all the companies that they deal with want C#
programmers.
I have read a book on C# (Teach yourself in 21 days, got it free from
codeguru for my Transparent Listbox), and I am reading the Wrox Beginner
C#
.net 2005 now. What I have noticed so far is that it is easy to develop
simple dialog base applications (I don't deny that), but it seems very
difficult when it comes to MDI applications. Specially in regards to
Docking
windows, menu/toolbar management. I also find it's event handling a bit
convoluted. It's just not easy to read, and know what events are being
handled and which ones aren't.

So the reason I asked this question here is that I wanted to know why
people
prefer C# over C++. I don't have enough expirence with C# to make a good
judgment about the language, but from what I have seen so far I find MFC
easier to deal with, and alot more flexiable than C#. So I wanted to find
out from people who actually use C# what they find like about it.

AliR.
"RobKinney1 " <Ro********@dis cussions.micros oft.com> wrote in message
news:CD******** *************** ***********@mic rosoft.com...

Hello AliR,

(usually I see you in the C++ sections!) Our company has decided to go

with

C# for our new devlopment for a few reasons (we still use C++ on a ddaily
basis).

It just works. It makes more sense and you use a lot fewer lines of code

to

do the same thing as in C++... Like with the TansparentStati c text... C#
already takes care of that automatically (your class saved my neck on a
deadline though for C++!).

The controls look a lot better.

Version control should be a lot better with the OneClick development
(compared to our current method).

Office automation (what a nightmare) is supposed to be easier and I have
been finding more documentation for it than with C++. ... Actually I
have
found more examples with VB.NET which I think we can still incorperate in

our

C# code (not sure how that works yet).

From what I have read there is supposed to be more consistancy accross

OS's

using C# (or just .NET in general) since it is the same framework. I
know

we

have had problems in the past between differnt Windows versions with some

of

the software we write in C++.

Sockets are supposed to be easier according to my comrade in the next

room.

He said something about SSL being built in to the .NET framework whereas

we

are having to use a 3rd party library for it in C++.

Alot of these things are just projections and things I have been told to

be

true... and with the little programming I have done so far, a lot of it
checks out. I am not a pro though (entry level, small company). Pleaes
don't hold me responsible for these comments if they are in error...
these
are the preconceptions I have about it from what I have read, etc... Can

any

one confirm these comments?

Rob K
"AliR" wrote:

> Hi All,
>
> The question is why should I use C#?
> If am developing a windows application, what are the advantages of
> using C# > versus VC++ (MFC)?
>
>
> Thanks
> AliR.
>
>
>

[Jeff Louie]

AliR... If you are a C++ programmer there is no need to change languages
with c++/cli. Just target the .NET framework in C++/cli and call native
code using ItJustWorksInte rop.

In the following C++/cli code demonstrating Resource Acquisition Is
Initialization, the destructor will be called when r goes out of scope.
This is an exception safe guarantee.

RAII r;
r.SayHello();
Console::WriteL ine(r.I);

Here is C++/cli syntax that a C# programmer should be able to read:

public ref class RAII
{
private:
int i;
bool isDeleted;
public:
RAII() : i(2), isDeleted(false )
{
Console::WriteL ine(L"Construct or called.");
}
~RAII() // maps to Dispose
{
if (!isDeleted) { // release once only
// clean up managed resources here.
Console::WriteL ine(L"Releasing managed resources.");
this->!RAII(); // clean up unmanaged resources here.
}
this->isDeleted= true;
Console::WriteL ine(L"Destructo r called.");
// finalize (!RAII) is automagically suppressed
};
!RAII() // maps to Finalize
{
if (!isDeleted)
{
// Clean up unmanaged resources here.
Console::WriteL ine(L"Releasing unmanged resources.");
}
Console::WriteL ine(L"Finalizer called.");
}
property int I {
void set(int value) {this->i = value;}
int get() {return i;}
}
// this can be called even after this object has been disposed!
// ASSERT isDeleted is false
void SayHello()
{
if (isDeleted) {
throw gcnew System::Invalid OperationExcept ion();
}
Console::WriteL ine(L"Hello");
}
void Close() {
if (!isDeleted) {
this->~RAII();
}
}
};

Here is a native C++ class with only a managed entry point:

public class Native {
public:
virtual int __clrcall Sum(int ai[], int size) {
int sum=0;
for(int i=0; i< size; i++) {
sum+= ai[i];
}
return sum;
}
};

Here is ItJustWorksInte rop:

int SumInteropClrCa ll(array<int>^ ai) {
pin_ptr<int> ppi= &ai[0];
Native n;
return n.Sum(ppi,ai->Length);
}
Regards,
Jeff

*** Sent via Developersdex http://www.developersdex.com ***