The developer world ready for .NET?

I have the impression that about half of the questions posed here are .NET
related.
Does that mean that the world of C++ developers is finally moving to managed
code and reducing the unmanaged code?

Or are these just simple experiments of students wondering what is all the
fuzz about .NET?

[Will]

<Ol**********@skyscan.be> wrote in message
news:41*********************@news.skynet.be...

Does that mean that the world of C++ developers is finally moving to managed code and reducing the unmanaged code?
Yes.
Or are these just simple experiments of students wondering what is all the
fuzz about .NET?

Yes.

Regards,
Will

[Steve McLellan]

> I have the impression that about half of the questions posed here are .NET

related.
Does that mean that the world of C++ developers is finally moving to managed code and reducing the unmanaged code?

Or are these just simple experiments of students wondering what is all the
fuzz about .NET?

Nope, we're using mixed C++. Mainly at the moment for UI code, since our
back end stuff's a) implemented using unmanageable external libraries and b)
we develop for the Mac and so, for the moment, keepe verything in C++ and
use Cocoa for the front end bits and bobs on the Mac. .NET's much, much
faster to get things developed than WIN32, and leaves less room for
hard-to-find mistakes.

Steve

[Gerhard Menzl]

Ol**********@skyscan.be wrote:

Does that mean that the world of C++ developers is finally moving to managed
code and reducing the unmanaged code?

The world of C++ developers is larger than you think. It encompasses
many platforms where .NET does not and will never play a role.

--
Gerhard Menzl

Humans may reply by replacing the obviously faked part of my e-mail
address with "kapsch".

[billr]

"Ol**********@skyscan.be" wrote:

I have the impression that about half of the questions posed here are .NET
related.
Does that mean that the world of C++ developers is finally moving to managed
code and reducing the unmanaged code?

Or are these just simple experiments of students wondering what is all the
fuzz about .NET?

This group is microsoft.public.dotnet.languages.vc, so I personally would expect 99% of the posts to be dotnet related, but maybe I'm just old fashioned.

> This group is microsoft.public.dotnet.languages.vc, so I personally would
expect 99% of the posts to be dotnet related, but maybe I'm just old
fashioned.

It is not that you have Visual Studio .NET that you must use the .NET
framework; ;-)

The reason why I asked the question is to have some arguments to other
developers, bosses and clients why would I use .NET managed code.

I perfer it because creating user interfaces is speeded up dramatically, and
at the same time I have access to all modern functionality including
remoting, xml which I will need in the future. The biggest problems I had,
was that it slowed down developing easy to install .NET applications, but
now I am at a level that I have 99% control over it so deployment is as
simple as install and run. :-) But I did los 90% of my hair in the process
to learn this thing. ;-)

..

[Steve McLellan]

> > This group is microsoft.public.dotnet.languages.vc, so I personally
would

expect 99% of the posts to be dotnet related, but maybe I'm just old
fashioned.

It is not that you have Visual Studio .NET that you must use the .NET
framework; ;-)

The reason why I asked the question is to have some arguments to other
developers, bosses and clients why would I use .NET managed code.

I perfer it because creating user interfaces is speeded up dramatically,

and at the same time I have access to all modern functionality including
remoting, xml which I will need in the future. The biggest problems I had,
was that it slowed down developing easy to install .NET applications, but
now I am at a level that I have 99% control over it so deployment is as
simple as install and run. :-) But I did los 90% of my hair in the process
to learn this thing. ;-)

For us, it came down to the tradeoff between potential problems deploying
versus the speed of development, mainly for UIs. I think deployment can be
handled properly and will rapidly become less of a problem (since the
framework is in Windows Update). I also think it's a valid point to make
that if you're developing applications (desktop or web) it's reasonably
certain that .NET is going to be pushed by MS in the coming years, so it's
not a bad idea to get people trained in it now. Plus it's good for you
personally, since it's another skill you have.

Good luck persuading people! :-)

Steve