The Full Wiki

More info on Shared Source Common Language Infrastructure

Shared Source Common Language Infrastructure: Wikis

Advertisements

Note: Many of our articles have direct quotes from sources you can cite, within the Wikipedia article! This article doesn't yet, but we're working on it! See more info or our list of citable articles.

Encyclopedia

From Wikipedia, the free encyclopedia

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.

Contents

History

Beginning in 2001, Microsoft announced they would release part of the .NET framework infrastructure source code in Shared source through ECMA, as part of the C# and CLI standardization process[1].

On March 2002, Microsoft released version 1.0 of the Shared Source Common Language Infrastructure, also called Rotor[2]. The Shared Source CLI was initially pre-configured to run on Windows, but could also be built on FreeBSD (version 4.7 or newer), and Mac OS X 10.2. It was designed such that the only thing that needed to be customized to port the Shared Source CLI to a different platform was a thin Platform Abstraction Layer (PAL).

The last 2.0 version of SSCLI was released on March 2006[3], and contains most of the classes and features of version 2.0 of the .NET Framework[4]. Unlike the previous version however, it is only supported on Windows XP SP2. Developers trying to build SSCLI 2.0 on Vista either failed or could not make .NET programs to run correctly, leading some to think that SSCLI would not be updated anymore[5].

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[6].

See also

References

  1. ^ "Microsoft Plans Shared Source .NET". ondotnet.com. 2001-06-27. http://ondotnet.com/pub/a/dotnet/2001/06/27/dotnet.html. Retrieved 2009-09-27. "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. ^ "Uncovering Rotor -- A Shared Source CLI". ondotnet.com/pub. 2002-03-204. http://ondotnet.com/pub/a/dotnet/2002/03/04/rotor.html. Retrieved 2009-09-27.  
  3. ^ "Shared Source Common Language Infrastructure 2.0 Release". Microsoft. 2006-03-23. http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=8c09fd61-3f26-4555-ae17-3121b4f51d4d. Retrieved 2009-05-21.  
  4. ^ Krause, Kristofer (2003-05-13). "A Beginner's Guide to Microsoft's shared Source CLI (Rotor)". c-sharpcorner.com. http://www.c-sharpcorner.com/UploadFile/kristoferkrause/GuidetoMSsharedSourceCLI11302005232759PM/GuidetoMSsharedSourceCLI.aspx. 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."  
  5. ^ Barnett, Granville (2008-12-08). "Shared Source CLI (aka Rotor) on Vista". http://msmvps.com/blogs/gbarnett/archive/2008/12/08/shared-source-cli-aka-rotor-on-vista.aspx. Retrieved 2009-05-21. "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. ^ 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

External links

Advertisements

Advertisements






Got something to say? Make a comment.
Your name
Your email address
Message