Shared Source Common Language Infrastructure

This is an old revision of this page, as edited by Hervegirod (talk | contribs) at 13:10, 21 May 2009 (update for the last SSCLI version). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The Shared Source Common Language Infrastructure (SSCLI), previously codenamed Rotor, is Microsoft's shared source implementation of the CLI, the core of .NET. Although the SSCLI is not suitable for commercial use due to its license, it does make it possible for programmers to examine the implementation details of many .NET libraries and to create modified CLI versions. Microsoft provides the Shared Source CLI as a reference CLI implementation suitable for educational use.

The Shared Source CLI was pre-configured to run on Windows, FreeBSD (version 4.7 or newer), and Mac OS X 10.2. It is designed such that the only thing that needs to be customized to port the Shared Source CLI to a different platform should be a thin Platform Abstraction Layer (PAL).

The last 2.0 version of SSCLI was released on March 2006[1], and contains most of the classes and features of version 2.0 of the .NET Framework[2]. Unlike the previous version however, it is only supported on Windows XP SP2.

License

The Shared Source CLI use the Microsoft Shared Source Common Language Infrastructure license. This license allows modifications and redistribution of the code for personal or academic usages, but they can't be used for commercial products[3].

See also

References

  1. ^ "Shared Source Common Language Infrastructure 2.0 Release". Microsoft. 2006-03-23. Retrieved 2009-05-021. {{cite web}}: Check date values in: |accessdate= and |date= (help)
  2. ^ Krause, Kristofer (2003-05-13). "A Beginner's Guide to Microsoft's shared Source CLI (Rotor)". c-sharpcorner.com. Retrieved 2008-10-05. 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. {{cite web}}: Check date values in: |date= (help)
  3. ^ As written in the license, examples of commercial purposes would be running business operations, licensing, leasing, or selling the Software, or distributing the Software for use with commercial products