Bit confused about CTS ...
-
Hi, After I have read several articles on msdn and other tech sites, I am now bogged now with a doubt. Is CTS a specification checked by CLR or a component in CLR? I read all about the goals of CTS. But inside the .NET framework how it is placed? Is it defined as a set of rules inside CLR, hence can I take it is a component ? Or is the CLR programmed to check the some specifications( which we call CTS) while executing a CLR compliant language? Please explain me to get more insight in to this. Thanks, mani
-
Hi, After I have read several articles on msdn and other tech sites, I am now bogged now with a doubt. Is CTS a specification checked by CLR or a component in CLR? I read all about the goals of CTS. But inside the .NET framework how it is placed? Is it defined as a set of rules inside CLR, hence can I take it is a component ? Or is the CLR programmed to check the some specifications( which we call CTS) while executing a CLR compliant language? Please explain me to get more insight in to this. Thanks, mani
The Common Type System is just a set of rules that defines a commonly used set of primitive types, like
System.Int32, that are used by all languages that the Common Language Runtime supports. These type are mapped to the types used in each language. For example,System.Int32is anintin C# and anIntergerin VB.NET. This makes it very easy for classes written in different languages to pass data back and forth without any custom, time-consuming, conversions. The CTS is a set of rules, or specifications, at the core of the CLR, not a module or a component. It's part of the Common Language Specification that every .NET compiler MUST adhere to to manitain compatibility with the .NET Framework.Dave Kreskowiak Microsoft MVP - Visual Basic