From PC to internet runtime
Comment A recent discussion with a friend about the origins of Microsoft's .NET runtime prompted a little research. How did it come about?
A quick search doesn't throw up any detailed accounts. Part of the problem is that much of it is internal Microsoft history, confidential at the time.
One strand, mentioned here, is Colusa's OmniVM:
OmniVM was based on research carried out by Steven Lucco at Carnegie Mellon University. Steven co-founded Colusa Software in February 1994 in Berkeley, California. Omniware was released in August 1995. Colusa started working with Microsoft in February 1996. Microsoft acquired Colusa Software on March 12, 1996. Steven is currently a senior researcher at the Microsoft Bay Area Research Center.
OmniVM was appealing to Microsoft because Colusa had already created Visual Basic and C/C++ development environments for the VM. The VM was also claimed to be capable of running Java.
Microsoft took to calling the VM by the name of CVM, presumably for Colusa Virtual Machine. Or perhaps this is where the code name Cool came into being. Other names used at Microsoft include Universal Virtual Machine (UVM), and Intermediate Language (IL).
Microsoft's Jason Zander, commenting to a story on this blog, does not mention OmniVM:
The CLR was actually built out of the COM+ team as an incubation starting in late 1996. At first we called it the "Component Object Runtime" or COR. That's why several of the unmanaged DLL methods and environment variables in the CLR start with the Cor prefix.
Still, the timing pretty much matches. If Lucco came to Microsoft in 1996, he could have been part of an incubation project starting later that year.
In June 1999 Microsoft previewed the Common Executable Format for Windows CE:
A demonstration on Common Executable Format (CEF), a new compiler target within the Visual C++(r) development system for Windows CE, was also presented. This compiler enables cross-processor portability within a category of devices, such as Palm-size PCs or Handheld PCs. A single program executable under CEF is translated to the native code on either the host PC or the device, as desired. This capability eliminates the need for developers to recompile an application for every possible processor on a given Windows CE-based appliance before bringing it to market, thus enabling them to support every version of a device (Palm-size or Handheld PC) quickly and easily.
In 2000 I interviewed Bob Powell, then at Stingray, who told me this in relation to .NET:
There was an early version of the system for Windows CE called the Common Executable Format (CEF). The Pocket PC, which uses around seven different processor types, and which has many different versions of the operating system, is a deployment nightmare. This problem was addressed by the CEF, which was a test case. What is now in the IL is a more refined version of that.
Hmm, now that Windows is coming to ARM alongside x86, this sounds like it could be useful technology ... though despite obvious similarities, I don't think CEF was really an early version of the CLR. Maybe the teams communicated to some extent.
It seems that the man who perhaps began the .NET Runtime is also at the center of the technology that might overtake it. ®
This article first appeared at Tim Anderson's IT Writing.
Sponsored: 2016 Cyberthreat defense report