The document provides an overview of the .NET platform and C# programming language. It discusses the .NET framework and common language runtime (CLR), introduces C# components like classes and delegates, and covers ASP.NET web development fundamentals such as the page lifecycle, master pages, and application/session state.

2. TOPICS
 Microsoft .NET Platform and Visual Studio
 .Net Stack
 Introduction to C#
 OOPS component of C#
 Assemblies and Modules
 Introduction to Asp.Net

3. FRAMEWORK VIEW

5. .NET Framework View
Framework Class Library
ADO.NET
Network
XML
Security
Threading
Diagnostics
IO
Etc.
Common Language Runtime
Memory Management Common Type System Lifecycle Monitoring
C# VB.NET C++.NET Other
Operating System
Visual
Studio
.NET
Common Language Specification
Windows FormsASP.NET
Web Services
ASP.NET Application Services
Web Forms Controls Drawing
Windows Application Services

6. .NET Platform Influential Factors
.NET
OOP JVM
GUI
Web
component-
based design
n-tier design

7. .Net Stack
VERSIONS

8. Introduction To C#
C# is a Type-safe object-oriented language run on the .NET
Framework.

9. E
X
E
C
U
T
I
O
N

10. Code Conversion

11. C# Components
 Namespaces
 Classes
 Methods and
Properties
 Delegates and Event
Handler
 Interfaces
 Exception Handling
 Data Types
 Arrays

12. C# Class View

13. Delegates
 A new concept that is central to the programming model of
the CLR.
 Delegates are like function pointers, but are actually type-
safe, secure, managed CLR objects.
 The CLR guarantees that a delegate points to a valid
method.
 You get the benefits of function pointers without the
dangers.
 Each delegate is based on a single method signature.
 Commonly used for callbacks.
 Delegates are basis of event handlers.

14. The Common Type System
 Reference types are type-safe object pointers. Allocated in the
“managed heap”
 Four kinds of reference types: Classes, arrays, delegates, and
interfaces.
 When instances of value types go out of scope, they are instantly
destroyed and memory is reclaimed.
 When instances of reference types go out of scope, they are garbage
collected.
 Boxing = converting an instance of a value type to a reference type.
Usually done implicitly through parameter passing or variable
assignments.
 UnBoxing = casting a reference type back into a value type variable.

15. The Common Type System
Primitive Types
Int16
Int32
Int64
Single
Double
Decimal
Boolean
Byte
Char
Currency
DateTime
TimeSpan
Object
ArrayString
Enum
ValueType Exception Delegate
Multicast
Delegate
Class1
Class2
Class3

16. Data Types
C# Type .NET Framework type
bool System.Boolean
byte System.Byte
sbyte System.SByte
char System.Char
decimal System.Decimal
double System.Double
float System.Single
int System.Int32
uint System.UInt32
long System.Int64
ulong System.UInt64
object System.Object
short System.Int16
ushort System.UInt16
string System.String

17. Array Declaration
 int[] table; //not int table[]
 int[] number;
number=new int[10];
number=new int[20];
 Single Dimensional Arrays : int[] numbers;
 Multi Dimensional Arrays : int[,] numbers;
 Jagged Arrays : int[][] numbers;

18. Assemblies
 A logical collection of one or more EXEs and DLLs
containing an application’s code and resources
 It contains
 Codes in MSIL
 Manifest (A metadata description of the code and
resources)

19. Introduction to ASP.NET Development

20. Asp.Net
 Simply Server side language
 Simplified page development model
 Modular, well-factored, extensible architecture
 Superior debugging and tracing support
 Compiled, not interpreted
 Rich caching support
 Web farm scalable session state
 Automatically detects and recovers from errors

21. Request And Respond

22. General Things to know
 Client Side Scripting
 Server Side Scripting
 HTML
 JavaScript
 CSS
 JQuery
 Ajax
 XML

23. Web Forms in .NET
 Separate Code & Design
 Rich Web Forms
 Drag & Drop Design
 Like WinForms

24. Understand the Web Form
 Page Directive
 Server side code
 Form
 Normal HTML Structure
 Server Controls

25. Design Page on Framework

26. ApplicationFile(Global.asax)
File in
Project

27. Configuration File(web.config)
File in
Project

28. You must Know
 Post Back
 communicates back to the server
 View State
 state stored in a hidden field on the page
 transported to the client and back to the server,
 Is not stored on the server

29. Page Life Cycle
PreInit Init
Init
Complete
PreLoad
Load
Control
events
Load
Complete
Pre
Render
Save
StateComplete
Render Unload

30. ASP.NET States
 Session State
 allows the state of objects (serializable) to be stored for a
single session (lifetime of the user’s browser or specific
timeout)
 Application State
 allows the state of objects (serializable) to be stored for
the application across different sessions.

31. Master Page
 Template to Other pages
Content place holder
Master aspx
aspx

32. Master Page Fusion in Content Page

33. Master Page View on Framework
A B
Point A is the Content Place Holder of Master Page that contains Content1
and Content2 of .aspx toward Point B.

34. Starting ASP.NET Development ..
 Web Application
 Recommended
 Compiles all pages into one DLL
 Faster on first load after deployment
 Must recompile whole site for code change