List of Figures


Chapter 2: .NET Objects

Figure 2-1: Managed execution in the common language runtime.
Figure 2-2: Different source code programming languages are compiled into MSIL.
Figure 2-3: Console output of sample TimeClient program.
Figure 2-4: Single-file and multifile assemblies.
Figure 2-5: Assembly manifest of our sample time component.
Figure 2-6: Global assembly cache viewer.
Figure 2-7: Adding a reference to a shared component.
Figure 2-8: ILDASM showing version of a server component.
Figure 2-9: ILDASM showing required version in a client.
Figure 2-10: The .NET Framework Configuration utility.
Figure 2-11: Setting binding policies.
Figure 2-12: Object-oriented programming inheritance.
Figure 2-13: ILDASM showing inheritance from System.Object.
Figure 2-14: The Visual Studio Object Browser showing the inheritance tree.
Figure 2-15: Client program demonstrating System.Object features inherited by time component.
Figure 2-16: Automatic memory management with garbage collection.
Figure 2-17: Memory management client application.
Figure 2-18: .NET client/COM object interaction via a runtime callable wrapper.
Figure 2-19: Locating COM objects for RCW generation.
Figure 2-20: Sample .NET client using a COM server.
Figure 2-21: Sample late binding program.
Figure 2-22: COM callable wrapper.
Figure 2-23: Registry entries made by RegAsm.exe.
Figure 2-24: Transactional .NET component installed in Component Services Explorer.
Figure 2-25: .NET component committing and aborting transactions.
Figure 2-26: Sample program demonstrating structured exception handling.
Figure 2-27: Structured exception handling diagram.
Figure 2-28: Access check in common language runtime code access security.
Figure 2-29: Security configuration files in the configuration utility.
Figure 2-30: Assigning permissions to a permission set.
Figure 2-31: Setting properties of a single permission.
Figure 2-32: Setting properties of a different permission.
Figure 2-33: Setting code group membership conditions.
Figure 2-34: Assigning a permission set to a code group.

Chapter 3: ASP.NET

Figure 3-1: Server delivering static Web pages.
Figure 3-2: Server dynamically generating Web pages based on client input.
Figure 3-3: The Web page produced by ASP after processing the HTML/ code mixture in Listing 3-1.
Figure 3-4: Simplest example of ASP.NET.
Figure 3-5: Choosing an ASP.NET Web Application in Visual Studio .NET.
Figure 3-6: Using the Toolbox to drag Web controls onto the form.
Figure 3-7: .ASPX page execution engine sequence.
Figure 3-8: The range validator control.
Figure 3-9: The hierarchical nature of web.config files.
Figure 3-10: The Web.Config Editor from Hunter-Stone.
Figure 3-11: Managing session state.
Figure 3-12: Session state management sample application.
Figure 3-13: ASP.NET session state process running as a system service.
Figure 3-14: Forms-based authentication.
Figure 3-15: Persistent cookie created by sample application.
Figure 3-16: Sample application for forms-based authentication.
Figure 3-17: Passport authentication.
Figure 3-18: Sample application for forms role authentication.
Figure 3-19: Trusted user model of authorization.
Figure 3-20: Impersonation/delegation model of authorization.

Chapter 4: .NET Web Services

Figure 4-1: User interface of Kazaa, an application containing dedicated Internet access.
Figure 4-2: Server-side view of XML Web services.
Figure 4-3: Client-side view of XML Web services.
Figure 4-4: Default screen generated by ASP.NET when you request the XML Web service base page.
Figure 4-5: ASP.NET responds with a page like this.
Figure 4-6: Results returned by the XML Web service.
Figure 4-7: Accessing time service through SOAP.
Figure 4-8: Sample application showing SOAP access to the XML Web service.
Figure 4-9: Proxy generator example.
Figure 4-10: Adding a Web reference in Visual Studio.
Figure 4-11: Class view of the TimeService reference.
Figure 4-12: Creating a new project in Visual Studio.
Figure 4-13: Visual Basic solution based on the ASP.NET Web Service template.
Figure 4-14: Sample program demonstrating the break-even point for chunkiness.
Figure 4-15: Sample service demonstrating session state and exception handling.
Figure 4-16: XML Web service security example workflow.
Figure 4-17: The Web Services Enhancement sample client
Figure 4-18: Use of SOAP filters in input and output.
Figure 4-19: Modification of a SOAP message by filters.
Figure 4-20: Password matching process of WSE SOAP filter.

Chapter 5: Windows Forms

Figure 5-1: A simple Windows Forms sample.
Figure 5-2: A more complex form created with Visual Studio.
Figure 5-3: The Visual Studio toolbox.
Figure 5-4: Windows Forms architecture for hosting ActiveX controls.
Figure 5-5: Dialog box offering choice of ActiveX controls to import into your project.
Figure 5-6: Visual Studio Object Browser showing methods and properties of generated wrapper class for Web Browser ActiveX control.
Figure 5-7: Windows Forms application using Web Browser ActiveX control.
Figure 5-8: The FancySchmancyWindowsFormsDemoVB sample application.
Figure 5-9: Repainting the invalid area of a form.
Figure 5-10: Adding a menu and menu items to a form.

Chapter 6: Data Access in .NET

Figure 6-1: OLE DB abstracts away the differences between different data providers.
Figure 6-2: ADO object using OLE DB.
Figure 6-3: ADO.NET architecture and objects.
Figure 6-4: The ADO.NET DataSet object.
Figure 6-5: Web page from the simplest ADO.NET sample.
Figure 6-6: Operation of the DataSet sample program.
Figure 6-7: The XML layout for the DataSet object.
Figure 6-8: Our sample client application.
Figure 6-9: The Edit Author’s Info dialog box.
Figure 6-10: Server Explorer within the Visual Studio .NET environment.
Figure 6-11: SQLDataAdapter object properties.
Figure 6-12: Generating a DataSet in Visual Studio .NET.
Figure 6-13: Class View showing strongly typed classes.
Figure 6-14: IntelliSense support in Visual Studio.

Chapter 7: Handling XML

Figure 7-1: XML document used as command or request and response between different systems.
Figure 7-2: The .NET XML serialization process.
Figure 7-3: Simplest serialization sample program.
Figure 7-4: Sample program showing serialization of rectangle with different types of points.
Figure 7-5: Sample program serializing polygon.
Figure 7-6: Sample program demonstrating DOM parser.

Chapter 8: Events and Delegates

Figure 8-1: A listener providing a sender with a callback object (delegate).
Figure 8-2: A sender calling delegates to fire events to a listener.
Figure 8-3: Disassembly view of the class that fires the event.
Figure 8-4: Visual Studio, placing a new component on a form.
Figure 8-5: C# Properties window showing events fired by the sample component.
Figure 8-6: Sample program demonstrating dynamic hookup of event handlers.
Figure 8-7: Sample program using delegates for asynchronous operation.
Figure 8-8: Asynchronous operation.

Chapter 9: Threads

Figure 9-1: Process containing threads.
Figure 9-2: Simplest threading sample application.
Figure 9-3: Pooled thread executing a delegate.
Figure 9-4: Synchronization sample program.
Figure 9-5: Complex threading sample program.

Chapter 10: .NET Remoting

Figure 10-1: Marshaling by value.
Figure 10-2: Marshaling by reference.
Figure 10-3: Debugger output window showing trace statements of object creation and call.
Figure 10-4: Activation sample client.
Figure 10-5: Singleton object architecture.
Figure 10-6: Single-call object architecture.
Figure 10-7: Client-activated object architecture.
Figure 10-8: Lifetime sample program.

Chapter 11: .NET Reflection

Figure 11-1: Metadata inside an assembly
Figure 11-2: XML serializer reading an object’s metadata to serialize it.
Figure 11-3: The reflection sample program
Figure 11-4: Dialog box showing properties of an assembly
Figure 11-5: Dialog box showing properties of a single type object
Figure 11-6: Dialog box displaying information for an individual method
Figure 11-7: Dialog box used for calling a method via reflection




Introducing Microsoft. NET
Introducing Microsoft .NET (Pro-Developer)
ISBN: 0735619182
EAN: 2147483647
Year: 2003
Pages: 110

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net