Common Language Integration in .Net Framework

Sign in to leave a comment.

• 

  Abhishek Bhat15y agoPosted Feb 2, 2011, 10:07 PM

  CLI stands for Common Language Infrastructure... CLI has CLS, CTS and few other things. CLS has rules defined for Common language support in Dotnet. CLS stands for Common Language Specifications. Check - http://en.wikipedia.org/wiki/Common_Language_Infrastructure
  • K

    knights15y agoPosted Feb 3, 2011, 12:20 AM

    Lets put it straight. http://www.ecma-international.org/publications/standards/Ecma-335.htm So this article along with the title is correct or incorrect. The right should rule and stay rather than wrong stay and ruin.
  • 

    Sam Hobbs15y agoeditedPosted Feb 2, 2011, 11:08 PMEdited Feb 2, 2011, 11:09 PM

    The Wikipedia is usually good for getting answers, but ECMA is the relevant standard.
• K

  knights15y agoPosted Feb 1, 2011, 11:29 AM

  It seems that its an effort to explain CLI (Common Language Infrastructure).Please check at "http://en.wikipedia.org/wiki/.NET_Framework#Common_Language_Infrastructure_.28CLI.29".Acronym definition also sounds different if thats the scenario. The same article by same author can be found at http://www.dotnetspider.com/resources/42017-Proof-How-can-you-say-Net-support-CLI-Common.aspx, which has its status as "pending" and the reason mentioned by website Admin is "Reason: Add proper summary && Reference: Content: Use proper title for your resources" I think its a nice idea for Admin of this website to use this feature if possible to track and freeze the content which is unclear for readers for some reason.
• 

  Sam Hobbs15y agoPosted Feb 1, 2011, 2:39 AM

  Are you sure that CLI is an acronym for Common Language Integration? See <http://social.msdn.microsoft.com/Search/en-US?query=%22Common%20Language%20Integration%22&ac=8>. I see nothing indicating any relevance to .Net; all I see is something that appears to be a mistake in the MSDN. Now see "Standard ECMA-335 Common Language Infrastructure (CLI)" at <http://www.ecma-international.org/publications/standards/Ecma-335.htm>. That CLI is truly critical to .Net; as far as I know, it is .Net. Finally, using unmanaged code, it is possible to compile source code from more than one compiler and link them together into one executable (exe) file. That is not possible using unmanaged code/compilers, so as far as I am concerned, .Net is less sophisticated in the area of language integration.