Download to read offline
More Related Content
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
.Net programming with C#
- 1. .NET Programming withC# Hanoi University of Science and Technology
- 2. Module 1: Overview ofthe Microsoft .NET framework
- 3. Overview of theMicrosoft .NET framework • The .NET framework • Common language runtime • The .NET framework class library • ADO.NET: Data and XML • XML Web service • Web forms and services
- 4.
- 5.
- 6.
- 7.
- 8.
- 9. The .NET frameworkclass library
- 10.
- 11.
- 12. Web forms andservices
- 13. Overview of Namespaces •Namespaces • Some commonly used namespaces • Other important namespaces
- 14.
- 15.
- 16. Some commonly usednamespaces • System.Console • System.Windows.Forms • System.Drawing • System.Reflection • System.Text • System.Collections • System.IO • System.Net • System.Net.Sockets • System.Runtime.Serialization • System.Runtime.Remoting.Channels • System.Web.Services
- 17. Other important namespaces •System.Threading • System.Data • System.Reflection
- 18. Module 2: Introduction toa Managed Execution Environment
- 19.
- 20. Writing a .NETapplication
- 21.
- 22. Demonstration: Hello World •Compile the source code from Visual Studio .NET Command Promt csc HelloDemoCS.cs • Running the resulting executable file and see the output Hello World using C#! • Viewing assembly metadata by using MSIL (ildasm.exe)
- 23.
- 24. Defining a Namespaceand a Class
- 25. Entry Points, Scopeand Declarations
- 26. Console Input andOutput
- 27.
- 28. Compiling and Runninga .NET Application
- 29.
- 30. The Process ofManaged Execution
- 31. The Process ofManaged Execution • Compilation outputs an executable module (PE – portable executable) • Microsoft Intermediate Language (MSIL): CPU-independent set of instructions that can be converted to native code efficiently • Type Metadata: types, members, references used by CLR at runtime • Resources: .jpg, .bmp, .wav,… • When a user executes a managed application: • Operating System loads CLR • CLR converts MSIL instructions to native code (only when needed - JIT) • JIT improve the memory usage and initialization time
- 32.
- 33.
- 34. Microsoft Intermediate Language •MSIL is a CPU-independent language • MSIL contains instructions for many common operations: • Creating and initializing objects • Calling methods • Arithmetic and logical operations • Control flow • Memory access • Exception handling • … • MSIL must be converted to CPU-specific (native) code by a JIT compiler
- 35.
- 36.
- 37.
- 38.
- 39. Just-In-Time Compilation • Thecode execution process • CLR loads class types and attach stub code to each method (can be considered as kind of pseudo-code) • For subsequent method calls, the stub directs program execution to CLR for compiling the method’s MSIL to native code • The stub code is replaced by the address of compiled native code • Future calls to a compiled method will not involve the JIT compiler
- 40.
- 41.
- 42.
- 43.
- 44. Module 3: Working withComponents
- 45.
- 46. An Introduction toKey .NET Framework Development Technologies
- 47. Windows Forms • Todevelop applications in which the client computer handles most of the application processing • System.Windows.Forms contains classes used to create Windows forms
- 48. Web Forms • Tocreate applications in which the primary user interface is a browser • Web Forms applications are platform-independent • System.Web contains classes to create Web Forms
- 49. XML Web Services •A programmable entity residing on a Web server and is exposed through standard Internet protocols • Programming using XML web services is similar to using COM-based component (local library) • XML web services are using SOAP for transferring messages from/to a Web server, SOAP is almost transparent to the developer
- 50. Creating a Simple.NET Framework Component
- 51. Creating a Simple.NET Framework Component • The component provides a simple wrappers for string array • String GetString(int i): return the string at index i • Read-Only Count: number of strings in the array • Structured exception handling
- 52. Using Namespaces andDeclaring the Class
- 53. Creating the ClassImplementation
- 54.
- 55.
- 56.
- 57. Creating a SimpleConsole Client
- 58.
- 59.
- 60.
- 61.
- 62. Demonstration: Creating aWindows Forms Client
- 63. Creating an ASP.NETClient
- 64. Writing the HTMLfor the ASP.NET Application
- 65. Coding the Page_LoadEvent Handler
- 66. Generating the HTMLResponse
- 67. Demonstration: Testing theASP.NET Client
- 68. Module 4: Deployment andVersioning
- 69.
- 70. Introduction to ApplicationDeployment
- 71. Common Concepts • Classlibraries are organized in hierarchical namespaces and stored in PE files (dll, exe) • A PE file may contain multiple namespaces and vice versa • Metadata describes all the classes and types • PE files and non-executable files are combined in to a assembly file • Metadata describes files in one assembly file, exported and imported classes and types
- 72. Simple Applications • Asimplest .NET app can be executed on any computer as long as .NET runtime is installed • No registry, no external dll, no registration… (like COM/COM++ or old DLL- based software)
- 73. Componentized Applications • Componentizedapplication deployment is more complicated depending on how it shares the components
- 74.
- 75.
- 76.
- 77.
- 78. Specifying a Pathfor Private Assemblies
- 79. A Strong-Named Assembly •A component may be shared among many unrelated applications. That component should be strongly named and located in the OS assembly cache • Let’s discuss about dll- sharing in the conventional way • How to call API dynamically • How the dll is located • What are the disadvantages • Let’s discuss about COM- based dll sharing
- 80.
- 81.
- 82. Creating Multiple Versionsof a Strong-Named Assembly
- 83.
- 84.
- 85. Deploying Multiple Versionsof a Strong- Named Assembly
- 86. Related Topics andTools
- 87.
- 88.
- 89. Module 5: Common TypeSystem
- 90.
- 91. An Introduction toCommon Type System
- 92. An Introduction toCommon Type System
- 93. An Introduction toCommon Type System • Value Types • Reference Types • Fields, Methods and Properties • Interfaces: merely description of methods, properties and events
- 94. Value Types vs.Reference Type
- 95.
- 96.
- 97.
- 98.
- 99.
- 100.
- 101.
- 102.
- 103.
- 104.
- 105.
- 106.
- 107.
- 108.
- 109.
- 110.
- 111.
- 112.
- 113.
- 114.
- 115.
- 116.
- 117.
- 118.
- 119.
- 120.
- 121.
- 122.
- 123.
- 124.
- 125.
- 126.
- 127.
- 128. Type Operators • is:determine if an object is of a specific type • as: convert an object to a specific type, if type is not matched null is return (it’s different from casting) • typeof: return the type of an object
- 129.
- 130.
- 131. How Boxing Works •Boxing: • A value type is coped from the stack to the heap • An object is allocated on the heap to store the value • Unboxing: • Value is coped from the heap to a variable on the stack • InvalidCastException may occur
- 132.
- 133.
- 134.
- 135.
- 136.
- 137.
- 138.
- 139.