Yoon Joong Kim. Department of computer Engineering Hanbat National University

Transcription

1 Yoon Joong Kim Department of computer Engineering Hanbat National University

2 Contents 1. Microsoft.NET History 2. What is Microsoft.NET - Goal/.NET Platform/issues and ideas 3. The Microsoft.NET Framework 4. Common Language Runtime - Goal/Concepts/Compilation and execution/services/multiple Language Support 5. Windows Form/Web Form/C#/ VB.NET 6. Web Programming 7. Web Services 8. Ex.1 An Simple Web Services Example Page 2

3 1. History of.net Framework(cont.) Microsoft started development of the.net Framework in the late 1990s, originally under the name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions of.net 1.0 were released. Version 1.0 of the.net Framework was released in February 2002 with visual studio.net. Version 3.0 is included with Windows Server 2008 and Windows Vista. Version 3.5 with Windows 7 and Windows Server 2008 R2. ] Version 4.0 alongside Visual Studio Version 4.5 alongside Visual Studio 2012 for Windows Vista or later. Support metro style apps for Windows 8. Page 3

4 1. History of.net Framework(cont.) Goal -.NET is a network platform whose goal is as follow: the users(application or terminal device) that are connected to each others on the network regardless of wire or wireless communicate and transfer their information in the form of XML from any device, anytime, anywhere.. - Make it incredibly easy to build powerful web applications and web services The.NET Compact Framework added - a reduced version of the framework - Available on the Windows CE platforms including Windows Mobile devices such as smartphones. - for mobile or embedded device use. - The.NET Micro Framework that is targeted at severely resourceconstrained devices. Page 4

5 1. History of.net Framework(cont.) Generation Version number Release date Development tool Distributed with February 2002 Visual Studio.NET N/A April 2003 Visual Studio.NET 2003 Windows Server November 2005 Visual Studio 2005 Windows Server 2003 R November 2006 Expression Blend Windows Vista, Windows Server November 2007 Visual Studio 2008 Windows 7, Windows Server 2008 R April 2010 Visual Studio 2010 N/A August 2012 Visual Studio Visual Studio 2013 Windows 8, Windows Server 2012 Windows 8.1, Windows Server 2012 R Page 5

6 1. History of.net Framework(cont.) WPF(Windows Presentation Foundation) - a new user interface subsystem and API based on XML and vector graphics, WCF(Windows Communication Foundation - a service-oriented messaging system which allows programs to interoperate locally or remotely similar to web services. WF(Windows Workflow Foundation) - allows for building of task automation and integrated transactions using workflows. Windows CardSpace, - a software component which securely stores a person's digital identities and provides a unified interface for choosing the identity for a particular transaction, such as logging in to a website LINQ(Language Integrated Query) - can be used to conveniently extract and process data from arrays, enumerable classes, XML documents, relational databases, and third party data sources. TPL(Task Parallel Library) Page 6

7 2. What is Microsoft.NET(cont.) The Microsoft.NET Platform Visual Studio.NET.NET Enterprise Servers SQL Server 2005 Win Server 2003 Exchange 2010.NET Framework CLR, C#, ASP.NET, etc..net Services e.g. Microsoft Passport(Windows Live ID) Operating System e.g. Windows XP, Windows 2000, Linux Page 7

8 2. What is Microsoft.NET(cont.) A platform - The.NET Framework - Visual Studio.NET -.NET Enterprise Servers - Database, messaging, integration, commerce, proxy, security, mobility, orchestration, content management -.NET Building Block Services - Passport } -.NET My Services( Hailstorm ) The focus of this program Page 8

9 2. What is Microsoft.NET(cont.) that new language C# the next version of Visual Basic Microsoft putting XML into everything the next version of ASP the next version of Visual Studio Microsoft trying to kill Java being able to run everything across the Net it s a good thing Page 9

10 2. What is Microsoft.NET(cont.) Initially announced as the latest release of everything Microsoft - ASP.NET, VB.NET, C#.NET, VisualStudio.NET With some big ideas - the new language C#, Object-Orient Language - got rid of VB at last - the Common Language Runtime (CLR) - platform independent c.f. JRE - language integration - shared libraries ->language independent - ability to develop and use software components over the web - XML based Web Services - simplified deployment of Windows software - Simple copy of assembly EXE or DLL without any register editing => the end of DLL hell Assembly format includes its information(self-description) Page 10

11 2. What is Microsoft.NET(cont.) With some big ideas(cont.) - no more mixing HTML and script code in ASP - Representation page and business logic page - Data Access - work with RDBMS through the ADO.NET. - Support XML and interoperate in any platform besides Windows Web Services - Web Component - Easy to create and use it - NET depends on - four internet standards : HTTP, XML, SOAP, UDDI. Page 11

12 2. What is Microsoft.NET(cont.) A set of technologies for developing and using components to create: - web forms - web services - windows applications Supports the software lifecycle - development - debugging - deployment - maintenance Page 12

13 3. The Microsoft.NET Framework XML based Web Services Web Forms ASP.NET Windows Forms Library classes for accessing data and XML (ADO.NET, SQL, XML, XSLT, LINQ) Library Framework Base classes (IO, string, collections, security) Common Language Runtime.NET Framework Component Stack.NET Framework Page 13

14 3. The Microsoft.NET Framework 1. A software framework developed by Microsoft that runs primarily on Microsoft Windows. 2. Framework Class Library (FCL) 3. Language interoperability 1. each language can use code written in other languages 2. across several programming languages. 4. Common Language Runtime (CLR) 1. An application virtual machine 2. provides services such as security, memory management, and exception handling. FCL and CLR together constitute.net Framework. Page 14

15 The Microsoft.NET Framework The.NET Framework and Visual Studio.NET VB C++ C# JScript Common Language Specification XML based Web Services Web Forms ASP.NET Windows Forms Library classes for accessing data and XML (ADO.NET, SQL, XML, XSLT, LINQ) Library Framework Base classes (IO, string, collections, security) Visual Studio.NET Common Language Runtime Page 15

16 The Microsoft.NET Framework.NET Framework Classes Services Description Discovery Protocols Caching Configuration OLEDB Design Collections Configuration Diagnostics Globalization System.Web System.Data UI HtmlControls WebControls Security SessionState SQL SQLTypes IO Net Reflection Resources System System.Windows.Forms Form Button MessageBox Drawing2D Imaging XSLT XPath Security ServiceProcess Text Threading ListControl System.Drawing Printing Text System.Xml Serialization Runtime InteropServices Remoting Serialization Page 16

17 The Microsoft.NET Framework.NET Framework Classes A set of standard class libraries Included in.net Framework, organized in a hierarchy of namespaces. The built-in APIs are part of ether System.* or Microsoft.* namespaces. Implements all functions of file reading and writing, graphic rendering, database interaction, and XML document manipulation, among others. available to all CLI compliant languages. Framework Class Library (FCL). a small subset of the entire class library and is the core set of classes that serve as the basic API of CLR.[12] Parts of FCL are in Classes in mscorlib.dll,system.dll,system.core.dll are available in.net Framework and also in.net Compact Framework, Microsoft Silverlight and Mono. Base Class Library (BCL) a superset of FCL and refers to the entire class library that ships with.net Framework. Also includes the expanded libraries for Windows Forms, ADO.NET, ASP.NET, Language Integrated Query (LINQ), Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF) and Workflow Foundation (WF). Page 17

18 The Microsoft.NET Framework.NET Core -.NET Core is a free and open-source partial implementation of the.net Framework. - It consists of CoreCLR and CoreFX, which are partial forks of CLR and BCL respectively. [13] NET Core comes with an improved JIT compiler, called RyuJIT. [14] Page 18

19 The Microsoft.NET Framework. Assemblies - Compiled CIL code is stored in CLI assemblies. - Portable Executable (PE) file format, common on Windows platform for all DLL and EXE files. - Each assembly consists of one or more files, one of which must contain a manifest bearing the metadata for the assembly. - The complete name of an assembly contains its simple text name, version number, culture, and public key token. Assemblies are considered equivalent if they SHARE the same complete name, excluding the revision of the version number. A private key can also be used by the creator of the assembly for strong naming. The public key token identifies which private key an assembly is signed with. Only the creator of the keypair (typically.net developer signing the assembly) can sign assemblies that have the same strong name as a previous version assembly, since the creator is in possession of the private key. Strong naming is required to add assemblies to Global Assembly Cache. Page 19

20 The Microsoft.NET Framework. Design issues - Interoperabilities - Access to COM components is provided in System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework; - access to other functionality is achieved using the P/Invoke feature. - Language independence -.NET Framework introduces a Common Type System (CTS) and Common Language Infrastructure(CLI). -.NET Framework supports the exchange of types and object instances between libraries and applications written using any conforming.net language. - Security -.NET Framework has its own security mechanism with two general features: Code Access Security (CAS), and validation and verification. Page 20

21 The Microsoft.NET Framework. Design issues - Portability - cross-platform implementations are available for other operating systems (see Silverlight and Alternative implementations). - Microsoft submitted the specifications for CLI (which includes the core class libraries, CTS, and CIL),[16][17][18] C#,[19] and C++/CLI[20] to both ECMA and ISO, making them available as official standards. - This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms. - Memory management - Garbage collector and this is more efficient than the java. - Simplified deployment -.NET Framework includes design features and tools which help manage the installation of computer software to ensure that it does not interfere with previously INSTALLED SOFTWARE, and that it conforms to security requirements. Page 21

22 Common Language Runtime Goal Development services - Deep cross-language interoperability - Increased productivity Deployment services - Simple, reliable deployment assembly format - Fewer versioning problems NO MORE DLL HELL Run-trim services - Performance - Scalability - Availability - Reliability - Security - safety Page 22

23 Common Language Runtime Programs can run on any platform for which the CLR has been implemented - just like the JVM CLR gives language integration - a class written in one language can be used by a class written in another - share exactly the same libraries The CLR is no longer only available for Microsoft operating systems - CLR for the.net framework - Mono Project for the Linux and BSD-based OS and MAC OS X. - Portable.NET Page 23

24 Common Language Runtime Compilation Source Code Assembly C++, C#, VB or any.net language Compiler csc.exe or vbc.exe DLL or EXE Page 24

25 Common Language Runtime Execution Model Source code VB Compiler C# Compiler C++ Compiler MSIL Assembly Assembly Assembly like Java bytecode (.exe or.dll) Ngen Common Language Runtime JIT Compiler Native code Managed Code Managed Code CLR Managed Code Unmanaged Code CLR Services:Loads and executes code, garbage collects etc Operating System Services Page 25

26 Common Language Runtime Services Code management Conversion of MSIL to native code Loading and execution of managed code Creation and management of metadata Verification of type safety Insertion and execution of security checks Memory management and isolation Garbage collection Handling exceptions across languages Interoperation between.net Framework objects, COM objects and Win32 DLLs Automation of object layout for late binding Developer services (profiling, debugging, etc.) Page 26

27 Common Language Runtime Multiple Language Support Common Type System(CTS) - Superset of the data types used by most modern programming languages Common Language Specification(CLS) - Subset of CTS that allows code written in different languages to interoperate What languages? - Microsoft C#, C++, VB.NET, Jscript - Third party - Perl, Ada, Cobol, Java, Fortran, Delphi - Eiffel, Smalltalk, Scheme, Oberon, Haskell, Python, - Only practical if the language supports some sort of encapsulation Page 27

28 Common Language Runtime Multiple Language Support Common Language Infrastructure(CLI) - The purpose of CLI is to provide language-neutral platform - The CLI code is housed in CLI assemblies(dll, exe) - the CLI specification describes the following four aspects: - CTS(Common Type System) - Metadata ( code in CIL) - CLS(Common Language Specification) - VLS(Virtual Execution System) Page 28

29 Common Language Runtime Multiple Language Support CLI Language - CLI language is language that conforms the CLI specifications - Common Intermediate Language(CIL) - Is a target language to be compiled by CIL language - Assembly CLI implementation - Such as CLR(Common Language Run), MONO, Portable NET - Can execute CIL languages Common CLI languages - A#(Ada), Boo(Python), C#, Java, Delphi, C++, Corba, Component Pascal, Eiffel, F#, IronPhython, IronRuby, IronLips, J#, Jscript, P#(Prolog), VB.NET - Page 29

30 Windows Forms Framework for building rich clients Built upon.net Framework, languages Rapid Application Development (RAD) Visual inheritance Anchoring and docking Rich set of controls Extensible controls Data-aware Easily hooked into Web Services ActiveX support Licensing support Printing support Advanced graphics Page 30

31 Web Forms Built with ASP.NET - Logical evolution of ASP New programming model - Event-driven/server-side controls - Rich controls(e.g. data grid, validation) - Data binding - Controls generate browser-specific code - Simplified handling of page state Page 31

32 Web Forms Allows separation of UI and code - Separation of concerns is a good thing - Cleaner, more maintainable code Uses.NET languages - C# - Not just scripting Components - Is easy to create and use XCOPY/FTP deployment Page 32

33 Web Forms Caching(pages, fragments, custom) Scalable session state management Tracing support ASP.NET is extensible Page 33

34 Language C# New language created for.net Safe, productive evolution of C++ - No the pointers Key concepts - Component-oriented - Everything is an object - Robust and durable code - Preserving your investment - Whatever that means Standard language - Approved as standard by ECMA(ECMA-344) and ISO(ISO/IEC ) Page 34

35 Languaes Visual Basic.NET Modernizes and simplifies Visual Basic - A modernized version of Visual Basic Now provides - Inheritance - Threading - Exception handling - Support for late biding - Whatever that is Page 35

36 The Web Programming Server-Client and 3 Tier architecture voice touch vision Browser (IE, FireFox, Opera) (HTML) Client (PC or MAC) HTTP Web Server) (Apache, IIS) (ASP,JSP,PHP) Web Server SQL Database Database Server Presentation Layer Client Web Application Layer Network Server Persistence Layer Page 36

37 Programming the Web Server-Side Code What is server-side code? - Software that runs on the server, not on the client - Receives input from - URL parameters - HTML form data - Cookies - HTTP headers - Can access server-side databases, servers, files, mainframes, etc. - Dynamically builds a customized HTML document response for a client Page 37

38 Programming the Web Server-Side Code Why server-side code? - Availability - You can reach the Internet from any browser, any device, any time, anywhere - Manageability - Does not require distribution of application code - Easy to change code - Security - Source code is not exposed - Once user is authenticated, can only allow certain actions - Scalability - Web-based 3-tier architecture can scale out Page 38

39 Programming the Web Server-Side Technologies Common Gateway Interface (CGI) (Script) - not language specific - Internet Server API (ISAPI) - MS IIS s API, Apache s API m_isapi - Netscape Server API (NSAPI) Active Server Pages (ASP) - now obsolete Java Server Pages (JSP) PHP Hypertext Processor (PHP) ColdFusion Markup Language(CFML) - Scripting Language for the JVM, the.net framework, Google App Engine. - ASP.NET Page 39

40 Programming the Web Active Server Pages(ASP) Technology to easily create server-side applications - A complete rip-off of the good work of Rasmus Lerdorf ASP pages are written in a scripting language - usually VBScript but also Jscript or PerlScript An ASP page contains static HTML ASP script is (was) commonly used to access and update a database. - 3-tier systems UI page and Code page in ASP.NET Page 40

41 Programming the Web in ASP.NET HTTP request (form data, HTTP header data) HTTP response HTML, XML ASP page (static HTML + server-side logic) ASP page in.net UI Page (static HTML ) + Code Page (server-side logic) Page 41

42 Web Services A programmable application software component - allow remote access to software components - via standard web protocols HTTP, XML, SOAP, UDDI, WSDL - exposes functionality over the Web Using ASP.NET framework - can create Web Services that others can use - can write a program that uses the Web Services With some properties - The idea of Web Services is not exclusive to Microsoft - Standard technology - The center of the.net architecture Page 42

43 Web Services Evolution of the Web HTML HTML HTML, XML XML Generation 1 Static HTML Generation 2 Web Applications Generation 3 Web Services Page 43

44 An simple Web Services Ex1. An simple Web Services - HelloWorld Generation of Web Service : int Add(int a, int b) using ASP.NET Web Service Client using objects of HttpRequest Web Service Client with proxy using.net Environment - OS : Window 7 - Framework :.NET Tool : Visual Studio Language : C# - Browser : Internet Explorer 9 Page 44

45 More Resources.NET XML - Page 45

46 Conditions Page 46