SSCLI

The Shared Source Common Language Infrastructure , also known as Shared Source CLI or SSCLI , former project name Rotor , is Microsoft's open source implementation of the Common Language Infrastructure (CLI). CLI in its various versions represents the core of .NET components including the runtime environment. Microsoft sees the Shared Source CLI as a reference implementation for use for educational purposes. Although SSCLI is not suitable for commercial use because of its license, it has nevertheless enabled programmers to get to know the details of the implementation of many .NET libraries and to use this knowledge to create their own customized and commercially usable versions of the CLI.

history

In 2001 Microsoft announced for the first time that the company would publish parts of the .NET Framework Infrastructure source code as part of the C # and CLI standardization process.

In March 2002 Microsoft released version 1.0 of the Shared Source Common Language Infrastructure, also called Rotor . The Shared Source CLI was originally configured for Windows as the target platform, but could just as easily be used for FreeBSD (version 4.7 or newer) and Mac OS X 10.2. The design was set up in such a way that the only thing that had to be adapted for porting the Shared Source CLI to a new platform was a thin abstraction layer (Platform Abstraction Layer, PAL).

The last version of the SSCLI was 2.0, which was released in March 2006. It contains most of the classes and innovations of Version 2.0 of the .NET Framework . In contrast to the previous version, it could only run on Windows XP SP2. Developers who tried to compile SSCLI 2.0 on Vista either failed because of themselves or were later unable to create correctly running .NET programs. This gave rise to the assumption that the SSCLI would not receive any further updates.

License

The Shared Source CLI comes with the so-called Microsoft Shared Source Common Language Infrastructure license. This license permits the modification and distribution of sources for personal and academic use. Use for commercial purposes, such as a software product, is not permitted.

literature

David Stutz: Shared Source CLI Essentials , O'Reilly 2003, ISBN 059600351X
Jason Whittington: Shared Source CLI Provides Source Code for a FreeBSD Implementation of .NET , in: MSDN Magazine, July 2002

Web links

Individual evidence

↑ David Sims, Tim O'Reilly , Rael Dornfest: Microsoft Plans Shared Source .NET . ondotnet.com. June 27, 2001. Retrieved September 27, 2009: “ On Wednesday, Microsoft announced plans to release what amounts to a shared-source version of its .NET infrastructure for Windows and FreeBSD. Specifically, Microsoft says it has been working with the ECMA standards body and will release ECMA versions of the Common Language Infrastructure (CLI), a C # compiler, and an ECMAscript compiler. The CLI is similar to the Java virtual machine, in that it acts as a translator between the .NET infrastructure and other platforms. Program manager Dave Stutz says Redmond will work with Corel to develop the code. "
^ Brian Jepson: Uncovering Rotor - A Shared Source CLI . ondotnet.com/pub. March 4, 2002. Retrieved September 27, 2009.
↑ Shared Source Common Language Infrastructure 2.0 Release . Microsoft . March 23, 2006. Retrieved May 21, 2009.
↑ Kristofer Krause: A Beginner's Guide to Microsoft's shared Source CLI (Rotor) . c-sharpcorner.com. May 13, 2003. Retrieved October 5, 2008: “ Most of the .NET framework class libraries are present except for ADO.NET, Windows Forms, Web Forms, and Web Services. Either you or the Rotor community will have to implement these. On a less painful note, remoting, networking, and XML functionality (and source) are included. "
↑ Shared Source CLI (aka Rotor) on Vista ( Memento from December 16, 2013 in the Internet Archive ): Granville Barnett My personal view is that the SSCLI project is doomed to spend the rest of its time only officially supporting that which it did when it was first released. If anyone knows any different then let me know. I couldn't find any information on the web hinting that it would be updated if only to support Vista.
↑ It is noted in the license that a commercial application e.g. B. the handling of business transactions, the licensing, the rental or the sale of the software, or the distribution of the software for use with commercial products applies.

[1] David Sims, Tim O'Reilly , Rael Dornfest: Microsoft Plans Shared Source .NET . ondotnet.com. June 27, 2001. Retrieved September 27, 2009: “ On Wednesday, Microsoft announced plans to release what amounts to a shared-source version of its .NET infrastructure for Windows and FreeBSD. Specifically, Microsoft says it has been working with the ECMA standards body and will release ECMA versions of the Common Language Infrastructure (CLI), a C # compiler, and an ECMAscript compiler. The CLI is similar to the Java virtual machine, in that it acts as a translator between the .NET infrastructure and other platforms. Program manager Dave Stutz says Redmond will work with Corel to develop the code. "

[2] Brian Jepson: Uncovering Rotor - A Shared Source CLI . ondotnet.com/pub. March 4, 2002. Retrieved September 27, 2009.

[3] Shared Source Common Language Infrastructure 2.0 Release . Microsoft . March 23, 2006. Retrieved May 21, 2009.

[4] Kristofer Krause: A Beginner's Guide to Microsoft's shared Source CLI (Rotor) . c-sharpcorner.com. May 13, 2003. Retrieved October 5, 2008: “ Most of the .NET framework class libraries are present except for ADO.NET, Windows Forms, Web Forms, and Web Services. Either you or the Rotor community will have to implement these. On a less painful note, remoting, networking, and XML functionality (and source) are included. "

[5] Shared Source CLI (aka Rotor) on Vista ( Memento from December 16, 2013 in the Internet Archive ): Granville Barnett My personal view is that the SSCLI project is doomed to spend the rest of its time only officially supporting that which it did when it was first released. If anyone knows any different then let me know. I couldn't find any information on the web hinting that it would be updated if only to support Vista.

[6] It is noted in the license that a commercial application e.g. B. the handling of business transactions, the licensing, the rental or the sale of the software, or the distribution of the software for use with commercial products applies.