C#.Net Migration - A2Z Dotnet

More documents

Recommendations

Info

Common Type System - CTS • The CLR defines the type system, CTS • All .NET languages map into the CTS • CLR types defined under the System Namespace • All .NET languages provide their own keywords that map to the underlying CTS types – <strong>C#</strong> int keyword == System.Int32 – VB.NET integer keyword = System.Int32 16
Common Type System (CTS) • CLR programming model is based on the CTS – CTS provides backbone for the CLR – CTS defines a core set of system types – CTS defines set of object-oriented programming features – CTS defines rules for creating user-defined types – all managed languages must map to the CTS 17
Page 1 and 2: C# .NET Migration Moving from Visua
Page 3 and 4: Agenda • The .NET Framework, The
Page 5 and 6: Managed and Unmanaged Code Managed
Page 7 and 8: Why a Runtime? • MTS and COM+ wer
Page 9 and 10: Run on Any Platform • Today mainl
Page 11 and 12: Platforms That Support .NET Framewo
Page 13 and 14: Concerns with MSIL • Easy to deco
Page 15: Obfuscated Code //Original Source C
Page 19 and 20: Common Language Specification (CLS)
Page 21 and 22: C# Types - extend CLS Types • Com
Page 23 and 24: C# and VB.NET - not as different as
Page 25 and 26: Properties public class Human { pri
Page 27 and 28: Implementing and using interfaces u
Page 29 and 30: Using Type Navigation Operators int
Page 31 and 32: Base classes • Every type has at
Page 33 and 34: Base/derived construction • Const
Page 35 and 36: Derivation and constructor flow of
Page 37 and 38: Using method dispatching modifiers
Page 39 and 40: Combining method modifiers abstract
Page 41 and 42: Destructors and IDisposable using S
Page 43 and 44: Culturally Very Different ;-) • C
Page 45 and 46: Operator Overloading using System;
Page 47 and 48: Unsafe Code Blocks • Must set com
Page 49 and 50: Documentation Comments-Output 49
Page 51 and 52: Assemblies and Versioning • Assem
Page 53 and 54: Assembly without strong name Notice
Page 55 and 56: Assembly with strong name Notice ve
Page 57 and 58: Client and Versioning • Client is
Page 59 and 60: Global Assembly Cache • One of th
Page 61 and 62: Creating a publisher policy assembl
Page 63 and 64: Agenda The .NET Framework and the
Page 65 and 66: Pattern • Notification typically
Page 67 and 68:
Delegate definition • Define dele
Page 69 and 70:
Target use of delegate • Target d
Page 71 and 72:
Registration • Create delegate ob
Page 73 and 74:
Summary of delegate use define dele
Page 75 and 76:
Remove delegate • Can remove dele
Page 77 and 78:
Events • Events give private data
Page 79 and 80:
Interoperability • Framework Clas
Page 81 and 82:
Using a VB6 DLL from C# .NET • CL
Page 83 and 84:
Platform Invoke - P/Invoke • P/In
Page 85 and 86:
MarshalAsAttribute parameters • C
Page 87 and 88:
.NET Interoperability with COM •
Page 89 and 90:
.NET Exposed for COM Clients using
Page 91 and 92:
Agenda The .NET Framework and the
Page 93 and 94:
ADO.NET Example public static void
Page 95 and 96:
DataSet Example public static void
Page 97 and 98:
Call to Action • Must master Fram
show all

C#.Net Migration - A2Z Dotnet

Create successful ePaper yourself

Delete template?

Save as template?