Namespace: It is a Collection of names wherein each name is Unique.
They form the logical boundary for a Group of classes.
Namespace must be specified in Project-Properties.
Assembly: It is an Output Unit. It is a unit of Deployment & a unit of versioning.
Assemblies contain MSIL code.
Assemblies are Self-Describing. [E. g. metadata, manifest]
An assembly is the primary building block of a .NET Framework application. It is a collection of functionality that is built, versioned, and deploymed as a single implementation unit (as one or more files). All managed types and resources are marked either as accessible only within their implementation unit, or by code outside that unit.
Table of Content
- Abstract Classes
- Access Specifiers
- ASP.NET 2.0 Interview Questions
- Assembly and Namespaces
- Authentication in .Net
- Authorization in .Net
- Boxing vs Unboxing
- Const vs Read-only
- Const vs Read-only
- Constants in .Net
- Constructors
- Constructors of Extended Classes
- Cursor point to TextBox
- Data Abstraction
- Data Encapsulation
- Destructors
- Example on Encapsulation
- Fields in .Net
- Focus method
- Function Overloading
- Garbage Collections
- Gridview with Paging
- Indexers in .Net
- Inheritance and Extended Classes
- Inheritance in .Net
- Inheritance n Extended Classes
- Members of a Class
- Methods and Events
- Namespace used in EventLog
- Object
- Overriding and Hiding
- Page Life Cycle
- Properties in .Net
- Ref vs Out parameter
- Server.transfer vs Response.redirect
- Signatures of Main[] fn
- State Management
- String vs String Builder
- Types of parameters
- Using Keyword
- Value type vs Ref type
- Versioning in .Net
- What are Class Methods
- What are Classes
- What are Constructors
- What are Delegates
- What are Objects
- What is View State
- When to OverLoad
Monday, May 31, 2010
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment