Overview of .Net Framework And CLR,CTS

Category: Education

Presentation Description

OVerview Presentation on .net framework with Commonlanguage runtime and CTS


By: bijaykumar (144 month(s) ago)

Excellent Ppt,thanks to uploader.

By: Kellin (145 month(s) ago)

Thank you very much!

Presentation Transcript

Overview on.Net Framework : 

Overview on.Net Framework

Contents : 

Contents .Net Overview. .Net Platform .Net Framework Design Goals. .Net Framework

.Net Overview : 

.Net Overview It provides a mew programming interface to windows services and APIs & integrates number of technologies that emerged from Microsoft technologies from 90s. The .Net platform consists of 5 separate products groups: (A) development tools & libraries.(Set of languages) (B) web services.(Commercial web services) (C) specialized servers.(.Net enabled servers) (D) devices.(.Net enabled, non-pc devices) (E) Based on Object Oriented Programming.

What is the need for .Net in Present Condition : 

What is the need for .Net in Present Condition The main strategy of .Net is to enable software as a service, and it is more than that, it responds to the following trends within the software industry. Distributed Computing.(simplifies the development of robust client/server and multi-tier(n-tier) applications) Componentization.(simplifies the integration of software components developed by different vendors) Enterprise services.(development of scalable enterprise applications without writing the code to manage transactions,security..) Web Paradigm Shifts.(web application development(TCP/IP), presentations(HTML),programmability(XML & SOAP)


.NET PLATFORM .Net Platform Consists of 5 main Components . The following figure represents the components. The lowest is the Operating System which can be variety of Windows Platform. On top of the OS specialized server products, include Biztalk server, commerce server, Exchange Server… Services are highly reusable across the web, Microsoft provides large no of them,.Net Passport, .Net Alerts.. At the top of them, VS.net makes possible the rapid development of the services and other applications. Visual Studio .NET . Net Enterprise .NET Framework .Net Building Servers Block services Operating System on Servers, Desktops and devices

.Net Framework Goals : 

.Net Framework Goals Applications as the service solution Today’s solutions are services as applications The future is not applications but services Desktop Services: Today’s application + optional Web Services Web Services: The application delivered to any device Today’s Internet “services” Delivered via Internet via a portal www.hotmail.com www.lycos.com Not “portable”: Can’t take it with you as you browse Some “intermediary” solutions exist: www.passport.com Browser, vendor, and device dependent Requires interactive access

.Net Framework Goals Contd… : 

.Net Framework Goals Contd… Language integration  COM supports language independence which means that you can develop a COM component in any language u want. Microsoft .net supports not only language independence, but also language integration (CTS Common Type System, CLS Common Language Specification), means that it can be inherit from Classes, exceptions and Polymorphism. Simplified development.  Since the inception of Microsoft environment we have seen Lots of APIs, MFCs, Active Template Library(ATL), Com interfaces, Vbscript, Jscript …, each and every time develop a new application, a new API has to be build or constructed a new design. In this it is overridden. Reliability.  Now a every platform was made commercial, in this few will be reliable in delivering the needs of the client or the end-user. Security  Microsoft has concentrated on the Security point as they run on the single desktop with a single thread execution. The problem became more critical when multiple users accessing the system, in overcoming this problem the Microsoft .net introduced CAS(code access security), it specifies the parts of the executable code not the all.

.Net Framework : 

.Net Framework

End of the .Net Overview : 

End of the .Net Overview

Common Language Runtime : 

Common Language Runtime The Common Language Runtime (CLR) is the platform (or execution engine) on which managed code runs. The CLR shares much in common with a traditional operating system, and as such is a useful piece of the .NET Framework to be familiar with if you will be writing managed code. Managed Code is the term applied to any software running on the .NET Framework.

Common Language Runtime Contd.. : 

Common Language Runtime Contd.. Common Language Runtime is the underpinning of the .NET Framework. CLR takes care of code management at program execution and provides various beneficial services such as memory management, thread management, security management, code verification, compilation, and other system services. The managed code that targets CLR benefits from useful features such as cross-language integration, cross-language exception handling, versioning, enhanced security, deployment support, and debugging.

Common Language Runtime Contd.. : 

Common Language Runtime Contd.. Common Type System (CTS) describes how types are declared, used and managed in the runtime and facilitates cross-language integration, type safety, and high performance code execution. The Common Language Specification (CLS) is an agreement among language designers and class library designers to use a common subset of basic language features that all languages have to follow.

Common Language Runtime contd.. : 

Common Language Runtime contd.. Highlights Common type system Mapping of data types. Programming language  Framework Just-in-time (JIT) compilers JIT compiles intermediary language (MSIL) into native code Highly optimized for platform or device Garbage collector Permission and policy-based security Exceptions Threading Diagnostics and profiling

Purpose Of CLR : 

Purpose Of CLR The CLR is the execution engine for this platform, and these are its requirements. Safe binary execution:- software to run software-components that originated across the network or Internet. Performance:- Internet development solutions opt for safety and flexibility, software to execute in the native machine language of the host system. Bug reduction :- software that targets the internet must be robust (If a client application crashes, it affects a single user. If a server application crashes it can affect thousands of users and cost a millions of dollars. ) Ease of integration :- software that targets the Internet must be able to integrate with all kinds of other software. This includes software that runs locally, software that runs remotely, and software written for a wide variety of platforms.

More .NET Framework : 

More .NET Framework Namespaces and Classes Hierarchical, unified class libraries Unified and extensible provide “system” and base functionality and services Object-oriented: everything is an object! The systems uses the same classes offered to you Interfaces The .NET (Service) contracts Types Byte, Sbyte, Single, Double, String, Int16, etc. These all map to the common type system

Understanding Managed Code : 

Understanding Managed Code Managed code is a big piece of the .NET Framework. Managed code is what your C# or VB.NET code becomes once you compile it. The reason managed code is so important is that through code management it is possible for your software to run in vastly different environments safely, securely, and efficiently. Intermediate Language IL is a binary assembly language that is compiled at runtime down to whatever machine language is appropriate for the host CPU. JIT compilation always happens with managed code, so managed code always executes in native machine language.

Code Management : 

Code Management Memory management :-The CLR maintains a managed heap that is used for all memory allocations. The CLR also cleans up objects that are no longer used. Security:- The CLR makes sure that code can not undermine a system if it is not trusted. Thread management :- Although you can create your own thread objects with managed code, the CLR maintains a thread pool which can be used by your software. Type safety :- At runtime the CLR checks all typecasting operations to be sure that the cast is valid. Code verification :- The CLR also asserts that all methods must have a return instruction. It is impossible for one instruction to run-over into the next. Code verification is another feature that makes code robust, and makes it safe to run un-trusted or semi-trusted components.

End of Common Language Runtime : 

End of Common Language Runtime

authorStream Live Help