Microsoft Technologies
Microsoft has a large number of servers and APIs that developers can choose to use. The Windows platform is over 20 years old now, so obviously some APIs have been deprecated. Determining which APIs to build your applications upon can have a big effect on your software development process, so choosing ones that are likely to be around a while is important.
This is a work in progress. To be listed here, a technology must be a Microsoft technology designed for developers - not something like Office that supports scripting, but rather something a developer might choose to build their product around.
1985
1991
1992
1993
1994
Windows 95
SAPI
Win32
DirectX
Exchange
OLE DB
Internet Explorer
COM+
Windows Media Player
Windows CE
ISAPI
ADO
WinInet
Windows 2000
The .NET Framework
Windows Forms
.NET Remoting
Web Services
Managed C++
Passport
ASP.NET
C#
Visual Basic.NET
Tablet PC
.NET Compact Framework
MapPoint Web Service
J#
InfoCard
Windows Communications Foundation
Windows Presentation Foundation
Windows Workflow Foundation
C++/CLI
WinFX
PowerShell
Any more? (If so, post them as comments).
September 30th, 2005 at 7:52 am
[...] The result is this list of Microsoft technologies upon which you can build software. I haven’t written out descriptions or predictions yet, but just coming up with the list, and then determining the year the technology was introduced, was a bit of a project. [...]
October 12th, 2005 at 12:41 pm
[...] Today my prediction is that WPF is basically demoware, and I’ll mark that on my Microsoft Technologies roadmap shortly. [...]
May 13th, 2007 at 12:53 am
Windows Managent Instrumentation (WMI)
[ http://www.microsoft.com/whdc/system/pnppwr/wmi/default.mspx ]
WS-Management (formerly known as WMX)
[ http://xml.coverpages.org/ni2004-10-08-a.html ]
[ http://www.microsoft.com/whdc/system/pnppwr/wsm/default.mspx ]