C#

  • Thread starter Thread starter news.microsoft.com
  • Start date Start date
N

news.microsoft.com

What amount of projects are in C# or managed code of any language for that
matter at MS? What has this saved, what kind of speed up in Dev time has
this gained.?

Would all future projects be managed that arnt low level apps?

Basically we would expect that every app from MS would be managed in the
future.


Would this be the same for other platforms, Linux et all that eventually get
MONO and dotGNU etc, and mac i presume in the future. in 10 years from now
would we be coding C# and .NET components inplace of COM and unmanaged C
for that matter?

What would be the status of the MS unmanaged APIs once everything is
covered in managed Libraries, would they be classified as unuspporetd and
for internal use only eventually and were only supported on the managed
APIs?
 
news.microsoft.com said:
What amount of projects are in C# or managed code of any language for that
matter at MS? What has this saved, what kind of speed up in Dev time has
this gained.?
Click to expand...
No one who knows is likely able to tell you, or really likely reading this
group anyway.
Would all future projects be managed that arnt low level apps?

Basically we would expect that every app from MS would be managed in the
future.
Click to expand...
Given the direction of Longhorn, I would expect most MS applications to
migrate to managed code. from explorer.exe right up to Visio, however the
majority will probably be MC++ for a long time to come
Would this be the same for other platforms, Linux et all that eventually get
MONO and dotGNU etc, and mac i presume in the future. in 10 years from now
would we be coding C# and .NET components inplace of COM and unmanaged C
for that matter?
Click to expand...
Who can say, 10 years from now is a blank slate as far as I know. We'll see
waht comes, ;). The guys doing gnome sure seem to like .NET(Mono)
What would be the status of the MS unmanaged APIs once everything is
covered in managed Libraries, would they be classified as unuspporetd and
for internal use only eventually and were only supported on the managed
APIs?
Click to expand...
Unmanaged api's will likely go the way of 16 bit apis,. maintained for
compatibility purposes, but new features will not be added to the API set.
 
Well, the "unmanaged API" will more be "internal API" than public once the
support stops for it. My point is, eventally to target windows (and others
in time) will be managed or yer on yer own.
 
news.microsoft.com said:
Well, the "unmanaged API" will more be "internal API" than public once the
support stops for it. My point is, eventally to target windows (and others
in time) will be managed or yer on yer own.
Click to expand...
Well, not quite. You can still, if for whatever odd reasons you want to,
call 16 bit functions in new code. They are depreciated, but documented to
some extent in the PSDK. I suspect win32 will reach the same status, frozen,
no updates, no extensions(except for maybe some minor 64 bit stuff), while
the managed API will start to gain access to new features.
 
news.microsoft.com said:
MC++ is managed code, C++ isnt. So MC++ would count under this .
Click to expand...

Yes, I was simply pointing out that C# isn't likely going to replace teh
existing C++ codebase, although C# modules will come into over time. I
wouldn't, for example, be surprised if Office 12's UI was written in C#,
assuming its written for Avalon.
 
Back
Top