Introduction to .net framework
104 likes•89,402 views
.NET is a versatile and managed programming framework that allows for cross-platform development and integrates various programming languages. It offers a common runtime environment that handles language interoperability, memory management, and security features while simplifying complex coding practices inherent in previous programming methods. This document compares traditional programming challenges with those solved by .NET, highlighting its architectural advantages such as the Common Language Runtime (CLR) and the Framework Class Library (FCL).
Introduction to .net framework
- 1. Introduction to .Net FrameworkNithyaVidhyaarthi
- 2. Before .NETWindows GUI development: Win32 API, MFC, Visual Basic, COMWeb development: ASPJava – “Write once, run anywhere.”Embrace and extend: Visual J++
- 3. Life As a C/Win32 API ProgrammerTraditional software development for the Windows.C developers are forced to contend with complex memory management and pointer arithmetic. It lacks the benefits provided by the object-oriented approachWhen you combine the thousands of global functions and data types defined by the Win32 API to an already formidable language, it is little wonder that there are so many buggy applications floating around today.
- 4. Life As a C++/MFC ProgrammerC++ is an object-oriented layeron top of C.
- 5. Programmers benefit from the famed “pillars of OOP” (encapsulation, inheritance, and polymorphism).
- 6. Microsoft Foundation Classes (MFC) provides a set of C++ classes that facilitate the construction of Win32 applications.
- 7. It wraps a “sane subset” of the raw Win32 API behind a number of classes, magic macros, and numerous code-generation tools (wizards).
- 8. Regardless of the helpful MFC, programming for Windows using C++ remains a difficult and error-prone experienceVisual Basic 6.0 ProgrammerAbility to build complex user interfaces, code libraries, and data access logic with minimal fuss and bother. VB6 hides the complexities of the raw Win32 API from view using integrated code wizards, intrinsic data types, classes, and VB-specific functions.Not fully object-orientedNo “is-a” relationships between types (i.e., no classical inheritance)No multithreaded applications unless you are willing to drop down to low-level Win32 API calls (which is complex at best and dangerous at worst).
- 9. Life As a Java/J2EE ProgrammerObject oriented with syntactic roots in C++. Java cleans up many unsavory syntactical aspects of C++. Java provides programmers with a large number of predefined “packages” that contain various type definitions. Limited ability to access non-Java APIs.Little support for truecross-language integration. Not appropriate for many graphically or numerically intensive applications. A better approach for such programs would be to use a language such as C++ where appropriate.
- 10. Life As a COM ProgrammerMicrosoft’s previous application development framework.reusable binary code.C++ programmers can build COM classes that can be used by VB6. Delphi programmers can use COM classes built using C. COM’s language independence is limited. COM has no support for classical inheritance). COM is extremely complex under the hood.The Active Template Library (ATL) provides a set of C++ classes, templates, and macros to ease the creation of COM types.
- 11. Windows DNA ProgrammerMicrosoft has been adding more Internet-aware features into its family of operating systems and products.
- 12. COM-based Windows Distributed interNet Applications Architecture (DNA) is quite complex.
- 13. Due to the simple fact that Windows DNA requires the use of numerous technologies and languages (ASP, HTML, XML, JavaScript, VBScript, COM(+), and data access API like ADO). The complete maze…Completely unrelated syntaxes. JavaScript has a syntax much like C, while VBScript is a subset of VB6. The result is a highly confused mishmash of technologies.Each language and/or technology has its own type system: An “int” in JavaScript is not quite the same as an “Integer” in VB6.
- 14. .Net, the RescuerOOPJVMGUI.NETWebcomponent-based designn-tier design
- 16. .Net providesIntegrated environmentInternet, Desktop , Mobile devicesconsistent object-orientedTo provide a portable environmentA managed environment
- 17. What Is .NET.NET is a framework New programming methodology.NET is platform independent / cross platform.NET is language-insensitive
- 19. .NET Application.NET FrameworkNarrow view of .Net applicationsOperating System + Hardware
- 20. .Net Framework
- 21. .Net Architecture.NET architecture is:multi-languagecross-platformbased on the CLR, FCL, and JIT technology.NET components are packaged as assemblies
- 23. .Net Technical ArchitectureVBC++C#Visual Studio.NETJScript…Common Language SpecificationWindowsFormsASP.NET: Web Servicesand Web FormsWindowsFormsADO.NET: Data and XMLBase Class LibraryCommon Language Runtime
- 24. Common Language RuntimeA common runtime for all .NET languagesCommon type systemCommon metadataIntermediate Language (IL) to native code compilersMemory allocation and garbage collectionCode execution and securityOver 15 languages supported todayC#, VB, Jscript, Visual C++ from MicrosoftPerl, Python, Smalltalk, Cobol, Haskell, Mercury, Eiffel, Oberon, Oz, Pascal, APL, CAML, Scheme, etc.Rational is working on Java compiler for CLR
- 25. The CLR ArchitectureBase Class Library SupportThread SupportCOM MarshalerType CheckerException ManagerSecurity EngineDebug EngineMSIL to NativeCompilers (JIT)CodeManagerGarbageCollector (GC)Class Loader
- 26. CLR Execution Model (Narrow)Code in VB.NETCode in C#Code in another .NET LanguageVB.NET compilerC# compilerAppropriateCompilerIL(IntermediateLanguage) codeCLR just-in-timeexecution
- 27. CLR Execution ModelSource codeVBC++C#UnmanagedComponentCompilerCompilerCompilerManagedcodeAssemblyIL CodeAssemblyIL CodeAssemblyIL CodeCommon Language RuntimeJIT CompilerNative CodeOperating System Services
- 28. How CLR works?
- 29. CLR based executionJIT CompilerAPP.exe OS ProcessCLR other FCL componentsCore FCLobj codeUnderlying OS and HW
- 30. Common Language RuntimeExecution EngineCompiles Microsoft Intermediate Language (MSIL) into native codeHandles garbage collectionHandles exceptionsEnforces code access securityHandles verificationManaged v. Unmanaged
- 31. Implications of CLR execution modelClients need CLR & FCL to run .NET appsavailable via Redistributable .NET FrameworkDesign trade-off…managed execution (memory protection, verifiable code, etc.)
- 32. portability:
- 33. slower execution?CLR and JIT compiling.Indirect execution of .Net applications.All .NET languages compile to the same CIL.The CLR transforms the CIL to assembly instructions for a particular hardware architecture.This is termed jit’ing or Just-in-time compiling.Some initial performance cost, but the jitted code is cached for further execution.The CLR can target the specific architecture in which the code is executing, so some performance gains are possible.
- 34. Advantages of CLRSupport for developer services (debugging)Interoperation between managed code and unmanaged code (COM, DLLs).Managed code environmentImproved memory handlingImproved “garbage collection”
- 35. Advantages of CLRJIT allows code to run in a protected environment as managed code.
- 36. JIT allows the IL code to be hardware independent.
- 37. CLR also allows for enforcement of code access security.
- 38. Verification of type safety.
- 39. Access to Metadata (enhanced Type Information)Common Language Infrastructure
- 40. CLI
- 41. Common Language InfrastructureCLI allows for cross-language development.
- 42. Four components:
- 43. Common Type System (CTS)
- 44. Meta-data in a language agnostic fashion.
- 45. Common Language Specification – behaviors that all languages need to follow.
- 46. A Virtual Execution System (VES).Common Type System (CTS)A specification for how types are defined and how they behave.no syntax specifiedA type can contain zero or more members:FieldMethodPropertyEvent
- 47. Common Type System (CTS)
- 48. CTS Data Types
- 49. Common Data TypesCLR provides a set of primitive types that all languages must support. The data types include:Integer—three types 16/32/64 bitsFloat—two types: 32/64 bitsBoolean and CharacterDate/time and Time spanThe primitive types can be collected intoArraysStructuresCombination of the two
- 50. Common Language Specification (CLS)Not all languages support all CTS types and featuresC# is case sensitive, VB.NET is notC# supports pointer types (in unsafe mode), VB.NET does notC# supports operator overloading, VB.NET does notCLS was drafted to promote language interoperabilityvast majority of classes within FCL are CLS-compliant
- 51. Comparison to JavaHello.javaHello.classJVMcompileexecuteSource codeByte codeHello.vbHello.exeCLRcompileexecuteSource codeCIL
- 52. Base Class Library @ FCL
- 53. Base Class LibrarySimilar to Java’s System namespace.Used by all .NET applicationsHas classes for IO, threading, database, text, graphics, console, sockets/web/mail, security, cryptography, COM, run-time type discovery/invocation, assembly generation
- 54. Framework Class Library @ BCLSingle consistent set of object oriented class libraries to enable building distributed web applications (Unified Classes)Built using classes arranged across logical hierarchical namespacesWork with all CLR languagesNo more “VBRun” or “MFC” divide
- 55. Example
- 56. Intermediate Language (IL).NET languages are not compiled to machine code. They are compiled to an Intermediate Language (IL).
- 57. CLR accepts the IL code and recompiles it to machine code. The recompilation is just-in-time (JIT) meaning it is done as soon as a function or subroutine is called.
- 58. The JIT code stays in memory for subsequent calls. In cases where there is not enough memory it is discarded thus making JIT process interpretive.Queries?
- 59. Contact me viaMail: [email protected] [email protected] network(s) / Services:arunprasadvidhyaarthi – skype, slideshare.comArun85prasad – twitter, gmail, live, yahoo.com Arun Prasad - facebook, orkutArunprasad – scribd.comMobile: +91 93446 20159
- 60. Thank you !!!
- 61. Disclaimer The names of Technologies, Product(s), Companies, Application(s), Tool(s), Utilities, etc provided with this material are intended to reference only. The name(s), brand name(s), trademark(s), registered trademark(s), logo(s), slogan(s) belong to their respective owners in the respective countries.