DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 9 of 9

Thread: wot is CLR

  1. #1
    lostguy Guest

    wot is CLR

    any 1 can explain me the architecture of CLR is that something like JVM ...and
    how it see IL of our application either through some file ..if yes then wot
    kind of file is there that contains IL code and can we just take is file
    to other machine and then we compile that to native code to get machine independancy

  2. #2
    Scott Hutchinson Guest

    Re: wot is CLR

    Running a .NET application without first installing the .NET Framework (if
    that is even possible) would be pretty useless because the application could
    not access any of the over 5,000 classes in the .NET Framework Class
    Library, which is one of the biggest advantages of .NET.

    Here is an excerpt from the "Overview of the .NET Framework":

    The .NET Framework is a new computing platform that simplifies application
    development in the highly distributed environment of the Internet. The .NET
    Framework is designed to fulfill the following objectives:

    a.. To provide a consistent object-oriented programming environment
    whether object code is stored and executed locally, executed locally but
    Internet-distributed, or executed remotely.
    b.. To provide a code-execution environment that minimizes software
    deployment and versioning conflicts.
    c.. To provide a code-execution environment that guarantees safe execution
    of code, including code created by an unknown or semi-trusted third party.
    d.. To provide a code-execution environment that eliminates the
    performance problems of scripted or interpreted environments.
    e.. To make the developer experience consistent across widely varying
    types of applications, such as Windows-based applications and Web-based
    f.. To build all communication on industry standards to ensure that code
    based on the .NET Framework can integrate with any other code.
    The .NET Framework has two main components: the common language runtime and
    the .NET Framework class library. The common language runtime is the
    foundation of the .NET Framework. You can think of the runtime as an agent
    that manages code at execution time, providing core services such as memory
    management, thread management, and remoting, while also enforcing strict
    type safety and other forms of code accuracy that ensure security and
    robustness. In fact, the concept of code management is a fundamental
    principle of the runtime. Code that targets the runtime is known as managed
    code, while code that does not target the runtime is known as unmanaged
    code. The class library, the other main component of the .NET Framework, is
    a comprehensive, object-oriented collection of reusable types that you can
    use to develop applications ranging from traditional command-line or
    graphical user interface (GUI) applications to applications based on the
    latest innovations provided by ASP.NET, such as Web Forms and XML Web

    The .NET Framework can be hosted by unmanaged components that load the
    common language runtime into their processes and initiate the execution of
    managed code, thereby creating a software environment that can exploit both
    managed and unmanaged features. The .NET Framework not only provides several
    runtime hosts, but also supports the development of third-party runtime

    For example, ASP.NET hosts the runtime to provide a scalable, server-side
    environment for managed code. ASP.NET works directly with the runtime to
    enable Web Forms applications and XML Web services, both of which are
    discussed later in this topic.

    Internet Explorer is an example of an unmanaged application that hosts the
    runtime (in the form of a MIME type extension). Using Internet Explorer to
    host the runtime enables you to embed managed components or Windows Forms
    controls in HTML documents. Hosting the runtime in this way makes managed
    mobile code (similar to Microsoft® ActiveX® controls) possible, but with
    significant improvements that only managed code can offer, such as
    semi-trusted execution and secure isolated file storage.

    Features of the Common Language Runtime
    The common language runtime manages memory, thread execution, code
    execution, code safety verification, compilation, and other system services.
    These features are intrinsic to the managed code that runs on the common
    language runtime.

    With regards to security, managed components are awarded varying degrees of
    trust, depending on a number of factors that include their origin (such as
    the Internet, enterprise network, or local computer). This means that a
    managed component might or might not be able to perform file-access
    operations, registry-access operations, or other sensitive functions, even
    if it is being used in the same active application.

    The runtime enforces code access security. For example, users can trust that
    an executable embedded in a Web page can play an animation on screen or sing
    a song, but cannot access their personal data, file system, or network. The
    security features of the runtime thus enable legitimate Internet-deployed
    software to be exceptionally feature rich.

    The runtime also enforces code robustness by implementing a strict type- and
    code-verification infrastructure called the common type system (CTS). The
    CTS ensures that all managed code is self-describing. The various Microsoft
    and third-party language compilers generate managed code that conforms to
    the CTS. This means that managed code can consume other managed types and
    instances, while strictly enforcing type fidelity and type safety.

    In addition, the managed environment of the runtime eliminates many common
    software issues. For example, the runtime automatically handles object
    layout and manages references to objects, releasing them when they are no
    longer being used. This automatic memory management resolves the two most
    common application errors, memory leaks and invalid memory references.

    The runtime also accelerates developer productivity. For example,
    programmers can write applications in their development language of choice,
    yet take full advantage of the runtime, the class library, and components
    written in other languages by other developers. Any compiler vendor who
    chooses to target the runtime can do so. Language compilers that target the
    ..NET Framework make the features of the .NET Framework available to existing
    code written in that language, greatly easing the migration process for
    existing applications.

    While the runtime is designed for the software of the future, it also
    supports software of today and yesterday. Interoperability between managed
    and unmanaged code enables developers to continue to use necessary COM
    components and DLLs.

    The runtime is designed to enhance performance. Although the common language
    runtime provides many standard runtime services, managed code is never
    interpreted. A feature called just-in-time (JIT) compiling enables all
    managed code to run in the native machine language of the system on which it
    is executing. Meanwhile, the memory manager removes the possibilities of
    fragmented memory and increases memory locality-of-reference to further
    increase performance.

    Finally, the runtime can be hosted by high-performance, server-side
    applications, such as Microsoft® SQL ServerT and Internet Information
    Services (IIS). This infrastructure enables you to use managed code to write
    your business logic, while still enjoying the superior performance of the
    industry's best enterprise servers that support runtime hosting.

    ..NET Framework Class Library
    The .NET Framework class library is a collection of reusable types that
    tightly integrate with the common language runtime. The class library is
    object oriented, providing types from which your own managed code can derive
    functionality. This not only makes the .NET Framework types easy to use, but
    also reduces the time associated with learning new features of the .NET
    Framework. In addition, third-party components can integrate seamlessly with
    classes in the .NET Framework.

    For example, the .NET Framework collection classes implement a set of
    interfaces that you can use to develop your own collection classes. Your
    collection classes will blend seamlessly with the classes in the .NET

    As you would expect from an object-oriented class library, the .NET
    Framework types enable you to accomplish a range of common programming
    tasks, including tasks such as string management, data collection, database
    connectivity, and file access. In addition to these common tasks, the class
    library includes types that support a variety of specialized development
    scenarios. For example, you can use the .NET Framework to develop the
    following types of applications and services:

    a.. Console applications.
    b.. Scripted or hosted applications.
    c.. Windows GUI applications (Windows Forms).
    d.. ASP.NET applications.
    e.. XML Web services.
    f.. Windows services.
    For example, the Windows Forms classes are a comprehensive set of reusable
    types that vastly simplify Windows GUI development. If you write an ASP.NET
    Web Form application, you can use the Web Forms classes.

    Scott Hutchinson

    "lostguy" <> wrote in message
    > any 1 can explain me the architecture of CLR is that something like JVM

    > how it see IL of our application either through some file ..if yes then

    > kind of file is there that contains IL code and can we just take is file
    > to other machine and then we compile that to native code to get machine

    > in

  3. #3
    Patrick Troughton Guest

    Re: wot is CLR

    What is "wot"?


  4. #4
    Patrick Steele [MVP] Guest

    Re: wot is CLR

    In article <3cab4273$1@> (from Patrick Troughton
    > What is "wot"?


    Patrick Steele
    Microsoft .NET MVP

  5. #5
    Eduardo Guest

    Re: wot is CLR

    "Patrick Steele [MVP]" <> escreveu

    > > What is "wot"?

    > Yes.



  6. #6
    stever Guest

    Re: wot is CLR

    i think he meant "wut"

    "Eduardo" <> wrote in message
    > "Patrick Steele [MVP]" <> escreveu
    > > > What is "wot"?

    > >
    > > Yes.

    > ROFL!
    > Eduardo

  7. #7
    dnb Guest

    Re: wot is CLR

    That should be "whut".

    "stever" <> wrote in message news:3cab6834@
    > i think he meant "wut"
    > "Eduardo" <> wrote in message
    > news:3cab4def$1@
    > > "Patrick Steele [MVP]" <> escreveu
    > >
    > > > > What is "wot"?
    > > >
    > > > Yes.

    > >
    > > ROFL!
    > >
    > > Eduardo
    > >
    > >


  8. #8
    Scott Hutchinson Guest

    Re: wot is CLR

    If I remember right, a wot = 1 N*m/sec.

    Scott Hutchinson

    "Patrick Troughton" <> wrote in message
    > What is "wot"?
    > /Pat

  9. #9
    Mike Mitchell Guest

    Re: wot is CLR

    On 3 Apr 2002 09:57:07 -0800, "Patrick Troughton"
    <> wrote:

    >What is "wot"?

    It was Chad who said this in WWII! Cor, you lot must be really wet
    behind the ears! Or young.



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
HTML5 Development Center
Latest Articles
Questions? Contact us.
Web Development
Latest Tips
Open Source

   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center