From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0115_01C39731.C8F29A80
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   The smaller number in the description below is a reference to new =
managed APIs.  Nothing below is referring to removing existing APIs.  I =
have no idea if any of numbers below are accurate.

   In regard to the claimed press release which refers to a web site not =
Microsoft's.  Real Microsoft press releases are posted on microsoft.com. =
 The one claimed to be a Microsoft press release is followed by a =
reference that is from Microsoft though not a press release.

Rich

  "Randall Parker"
 =
wrote in message news:3f947b93$1{at}w3.nls.net...
  Can Rich or someone else tell us what the likely future is for various =

  Win32 APIs? My guess is that .NET will have fewer calls than Win32 but =

  that all (or at least 99% of them) of the Win32 calls will continue to =

  be there. I can't imagine an OS vendor pulling large numbers of calls=20
  out of an OS.

  Elsewhere I'm arguing that there is no way MS is going to remove API=20
  calls from the next version of Windows - at least not a large number.=20
  But the advocates of the idea that Win32 APis are going to get yanked =
in=20
  mass numbers are quoting these pages:


       http://msdn.microsoft.com/chats/vstudio/vstudio_121802.asp

       Q: Can you clarify the distiction between the WinForm API and the =

  future
  porting of Win32 to run as a managed API?

       A: The "Windows Forms" API is essentially a set of interfaces =
that
  expose the existing Win32 functionality via managed code. In the =
future, you
  will see the API for developing applications on Windows will evolve =
into a
  fully managed API.


  Here is a press release regarding some of Microsoft's plans for =
Longhorn:

       http://www.develop4.net/news.html

       First, the software giant aims to slash the number of API calls =
in the
  Win32 API set from more than 70,000 to fewer than 10,000 to help =
developers
  better exploit the next-generation Windows shell, user interface =
(code-named
  Aero) and .Net framework components in Longhorn, according to sources
  familiar with the Longhorn plans.

       "Win32 has like 76,000 APIs, and they're taking it down to 8,000 =
with
  Longhorn technology," said one source familiar with the plans.

       ...

       Also in Longhorn, Microsoft plans to integrate a replacement for =
the
  Windows graphics device interface (GDI), code-named Avalon...



  According to Eric Rudder, Senior Vice President of Developer and =
Platform
  Evangelism at Microsoft (and reiterated by Thomas Scheidegger, =
Microsoft's
  .NET MVP):

       http://www.microsoft.com/presspass/exec/ericr/02-11vslive.asp

       You'll see new UI tools and designers to take advantage of the =
new
  presentation system of "Longhorn." We'll leverage some new storage =
features
  of "Longhorn." And really if you think about where we're going with
  "Longhorn" it's really the next evolution of the Windows platform API. =
So
  you can think about Win 16 to Win 32 to really a managed platform =
where all
  the interfaces in Windows are managed.

------=_NextPart_000_0115_01C39731.C8F29A80
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   The
smaller number in the =
description=20
below is a reference to new managed APIs.  Nothing below is =
referring to=20
removing existing APIs.  I have no idea if any of numbers below are =

accurate.
 
   In regard
to the claimed =
press release=20
which refers to a web site not Microsoft's.  Real Microsoft press
= releases=20
are posted on microsoft.com.  The one claimed to be a Microsoft = press=20
release is followed by a reference that is from Microsoft though not a = press=20
release.
 
Rich
 

  "Randall Parker" <STOPt=">mailto:STOPtechieSPAMpunditNOW{at}STOPfutureSPAMpundit.comNOW">STOPt=
echieSPAMpunditNOW{at}STOPfutureSPAMpundit.comNOW>=20
  wrote in message news:3f947b93$1{at}w3.nls.net...Can=20
  Rich or someone else tell us what the likely future is for various =
Win32=20
  APIs? My guess is that .NET will have fewer calls than Win32 but =
that all=20
  (or at least 99% of them) of the Win32 calls will continue to be =
there. I=20
  can't imagine an OS vendor pulling large numbers of calls out of =
an=20
  OS.Elsewhere I'm arguing that there is no way MS is going to =
remove=20
  API calls from the next version of Windows - at least not a large =
number.=20
  But the advocates of the idea that Win32 APis are going to get =
yanked in=20
  mass numbers are quoting these =
pages:    =20
  http:=">http://msdn.microsoft.com/chats/vstudio/vstudio_121802.asp">http:=
//msdn.microsoft.com/chats/vstudio/vstudio_121802.asp &n=
bsp;  =20
  Q: Can you clarify the distiction between the WinForm API and the=20
  futureporting of Win32 to run as a managed=20
  API?     A: The
"Windows Forms" API is =
essentially=20
  a set of interfaces thatexpose the existing Win32 functionality =
via=20
  managed code. In the future, youwill see the API for developing=20
  applications on Windows will evolve into afully managed=20
  API.Here is a press release regarding some
of Microsoft's =
plans=20
  for Longhorn:     http://www.develop4.net/news.h" target="new">http://www.develop4.net/news.h=">http://www.develop4.net/news.html">http://www.develop4.net/news.h=
tml    =20
  First, the software giant aims to slash the number of API calls in=20
  theWin32 API set from more than 70,000 to fewer than 10,000 to =
help=20
  developersbetter exploit the next-generation Windows shell, user =
interface=20
  (code-namedAero) and .Net framework components in Longhorn, =
according to=20
  sourcesfamiliar with the Longhorn =
plans.    =20
  "Win32 has like 76,000 APIs, and they're taking it down to 8,000=20
  withLonghorn technology," said one source familiar with the=20
  plans.     =
...    =20
  Also in Longhorn, Microsoft plans to integrate a replacement for=20
  theWindows graphics device interface (GDI), code-named=20
  Avalon...According to Eric
Rudder, Senior Vice =
President of=20
  Developer and PlatformEvangelism at Microsoft (and reiterated by =
Thomas=20
  Scheidegger, Microsoft's.NET
MVP):     =
ht=">http://www.microsoft.com/presspass/exec/ericr/02-11vslive.asp">ht=
&n" target="new">tp://www.microsoft.com/presspass/exec/ericr/02-11vslive.asp&n=
bsp;   =20
  You'll see new UI tools and designers to take advantage of the=20
  newpresentation system of "Longhorn." We'll leverage some new =
storage=20
  featuresof "Longhorn." And really if you think about
where we're =
going=20
  with"Longhorn" it's really the next evolution of the Windows =
platform API.=20
  Soyou can think about Win 16 to Win 32 to really a managed =
platform where=20
  allthe interfaces in Windows are =
managed.

------=_NextPart_000_0115_01C39731.C8F29A80--

--- BBBS/NT v4.01 Flag-5