• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Microsoft .NET (dotnet) Framework 2003 - 2004 overview and web services…
 

Microsoft .NET (dotnet) Framework 2003 - 2004 overview and web services…

on

  • 496 views

C# in its early days...

C# in its early days...

Statistics

Views

Total Views
496
Views on SlideShare
496
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Microsoft .NET (dotnet) Framework 2003 - 2004 overview and web services… Microsoft .NET (dotnet) Framework 2003 - 2004 overview and web services… Presentation Transcript

    • Microsoft .NETFramework Overview Lorenz Sauer Jun 2004 / HTLW16
    • What is .NET?• Microsoft’s “vision” or marketing strategy, as well as new technologies• A brand applied to a new technology• Most significant new technologies – Common Language Runtime (CLR) – Common Language Infrastructure (CLI) – Web Services• Dawn of a new era of computing?
    • Benefits• Better integration of web services• Platform, that is OS independent• Language independence – Programming in your choice of language• Sophisticated Base layer, - the “framework“• Improves reliability, scalability, performance, and security
    • The .NET Framework• Windows “Standard” .NET Framework• Embedded Compact .NET Framework• .NET Framework class library• Common Language Runtime (CLR)
    • Framework Principle .NET Framework Applications Platform Specific Class Libs Base Class Libs Execution Engine (MSCOREE.DLL) Platform Adaptation Layer Host Operating System
    • Framework Blueprint .NET Framework.Net Compliant Language Windows Forms, (VC, VB.NET, ASP.NET, Web Forms, C#, JS.NET, J# Web Services others 3rd party) .NET Framework Base Classes (ADO.NET, XML, Threading, Diagnostics, IO, Net, Secutity etc. Common Language Runtime (Memory Management, Common Type System, Lifecycle Monitoring)
    • The .NET Class Library• Object-oriented collection of reusable classes• “System” namespace – All Framework classes• Accessible by a .NET language• Includes: – Database, rendering, file access & IO, diagnostics, object collections – Security, Reflection, Threading and Eventing
    • The .NET Class Library• Some Core types: – Char – Boolean – Int16 – Array• Also: – Console – Math – GC (Garbage Collection)
    • Common Language Runtime (CLR)• Manages memory• Thread execution• Code execution• Type safety verification• Lifespan / Lifetime Management• Compilation (Just In-time Compiler)
    • Common Language Infrastructure (CLI)• Subset of the CLR submitted to ECMA standards organization• Submitted for standardization: – C# – Semantics for metadata – Microsoft Intermediate Language (MSIL) – Parts of the .NET framework class library
    • Common Type System (CTS)• A single type system shared by compilers, tools and the CLR• Common type support for different languages• Types – Reference (heap allocation) – Value (stack allocation)
    • Common Language Specification (CLS)• Comprises a subset of CTS• A programming language must support CLS – For compliance with the .NET Framework• Contract: – between language designers and the .NET Framework
    • Managed Code• Software written for the CLR is referred to as managed code• Most significant concepts in managed code: – Assemblies – Microsoft Intermediate Language (MSIL)
    • Assemblies• code libraries compiled for CLR• make up a logical unit of functionality• Eases deployment, versioning and security.• A scheme for organizing code compiled for the CLR• Manifest describes dependencies, versions, scope• Contains Microsoft Intermediate Language (MSIL)
    • The Microsoft Intermediate Language (MSIL)• Intermediate code that runs in the CLR• Not a machine specific binary but an intermediate machine code representation• Must be converted by a .NET Framework: – just-in-time (JIT) compiler translates to native code
    • MSIL Tools• MSIL Assembler (Ilasm.exe) – Generates executable from MSIL• MSIL Disassembler (Ildasm.exe) – Creates MSIL code from executable• Native Image Generator Tool (Ngen.exe) – Compiles MSIL to machine code in lieu of JIT compiler
    • MSIL “Hello World”• Assembler directives begin with a period• MSIL Instructions lines: 8, 9 and 101. /* this is an MSIL comment */2. .assembly extern mscorlib {}3. .assembly hello {}4. .method static public void main() il managed5. {6. .entrypoint7. .maxstack 18. ldstr "Hello world!"9. call void [mscorlib]System.Console::WriteLine(class System.String)10. ret11. }
    • .NET Languages• The CLR was designed to support multiple languages: – C# – VB – C++ – J# – -…
    • C#• Fully tailored to .NET• Twice as comprehensive as of C++• C++ scope available via virtual declaration• Powerful COM-InterOp• Programmer decides when to use Managed Envionment and when not: – Shallow learning curve
    • Web Technologies• The .Net XML Web services are distributed, server- side applications• XML Web services built on industry standards – XML – WSDL – SOAP – UDDI – WSDL
    • XML• XML provides a way to describe information in a structured format• Tag based <….> content </…>• Attributes, values, rules…• Document trees and hierarchies via “nesting”• Supported by the World Wide Web Consortium (W3C)
    • WSDL• XML based language used to define Web services interfaces• Similar to IDL for COM and CORBA (Common Object Request Broker Architecture)
    • SOAP• Provides an XML envelope for data exchange in distributed networks• Message consists of three parts: – Envelope that defines a framework for describing what is in a message and how to process it – Encoding rules for expressing instances of application- defined data types – Convention for representing remote procedure calls (RPCs) and responses
    • UDDI• Umbrella organization of businesses• Goal: expose web services through a registry• The Registry is itself a web service – provides information about other web services – provides information about integration
    • Open Standards• CLI, C# submitted to ECMA standards organization• Open source implementations of the .NET Development Framework and C# – Mono project by Ximian – The GNU open source organization
    • Resources •Based upon: Eric Landry, Microsoft .NETFramework Overview, A Presentation •UDDI Homepage •http://www.uddi.org/ •EMCA filing of CLI and C# •http://www.ecma.ch/ecma1/STAND/ecma-335.htm
    • Resources•The Mono Project homepage•http://www.go-mono.com/•The dotGNU Homepage•http://www.dotgnu.org•Microsoft’s .NET Homepage•http://www.microsoft.com/net/