View State: 

- View state is maintained in page level only.
- View state of one page is not visible in another page.
- View state information stored in client only.
- View state persist the values of particular page in the client (browser) when post back operation done.
- View state used to persist page-instance-specific data. (Read more)

      Session State: 

- Session state is maintained in session level.
- Session state value is available in all pages within a user session.
- Session state information stored in server.
- Session state persist the data of particular user in the server. This data available till user close the browser or session time completes.
- Session state used to persist the user-specific data on the server side. (Read more)   

Difference between an EXE and a DLL

hi,
   DLL:
1)it has versioning
2)it is not self executable
3)it runs in application process memory
4)it has no entry point
5)it is reusable
6)Out Process Server
 
Exe:
1)it is self executable
2)it has no versioning
3)it runs in own memory
4)it have main function(Entry point)
5)it is self executable
6) In Process Server
 
Note:DLL is Superset of Exe

Freelancer

Web Search Freelancer

What is Inheritance in C#

Inheritance can be classified to 5 types.
1.Single Inheritance
2.Hierarchical Inheritance
3.Multi Level Inheritance
4.Hybrid Inheritance
5.Multiple Inheritance

1. Single Inheritance when a single derived class is created from a single base class then the inheritance is called as single inheritance.

Single Inheritance Example Program

2. Hierarchical Inheritance
when more than one derived class are created from a single base class, then that inheritance is called as hierarchical inheritance.

Hierarical Inheritance

3. Multi Level Inheritance
when a derived class is created from another derived class, then that inheritance is called as multi level inheritance.

Multi level Inheritance

4. Hybrid Inheritance
Any combination of single, hierarchical and multi level inheritances is called as hybrid inheritance.

Hybrid inheritance in C#

5. Multiple Inheritance
when a derived class is created from more than one base class then that inheritance is called as multiple inheritance. But multiple inheritance is not supported by .net using classes and can be done using interfaces.

Multiple inheritance in C# Multiple Inheritance Example

Handling the complexity that causes due to multiple inheritance is very complex. Hence it was not supported in dotnet with class and it can be done with interfaces.

Create Your Password Protected Folder

Before you get started you need to create a folder that will house your password protected folder, this is just an ordinary folder and can be located anywhere and named anything. Navigate into your newly created folder and create a new Text Document. This can easily be done from the context menu. Open the document, now paste the following code into the contents of the document: cls @ECHO OFF title Folder Private if EXIST "HTG Locker" goto UNLOCK if NOT EXIST Private goto MDLOCKER :CONFIRM echo Are you sure you want to lock the folder(Y/N) set/p "cho=>" if %cho%==Y goto LOCK if %cho%==y goto LOCK if %cho%==n goto END if %cho%==N goto END echo Invalid choice. goto CONFIRM :LOCK ren Private "HTG Locker" attrib +h +s "HTG Locker" echo Folder locked goto End :UNLOCK echo Enter password to unlock folder set/p "pass=>" if NOT %pass%== PASSWORD_GOES_HERE goto FAIL attrib -h -s "HTG Locker" ren "HTG Locker" Private echo Folder Unlocked successfully goto End :FAIL echo Invalid password goto end :MDLOCKER md Private echo Private created successfully goto End :End Change the PASSWORD_GOES_HERE text to the password you want to set. Now go ahead and save the file as locker.bat. Once the file is saved as a batch file you can delete the original text file. Now run your batch file by double clicking on it–the first time you run it, it will create a folder called Private. This is where you can store all your secret things. When you have finished adding all your stuff to the Private folder, run locker.bat again. This time you will be asked if you sure that you want to lock the folder, press the “Y” key and hit enter to lock your folder. You will see that your Private folder quickly disappears. If you run the script yet again, you will prompted for a password. If you enter the same password as you set in the script the Private folder will reappear if you enter the incorrect password the script will just Terminate.

System Development Life

System Development Life Cycles fall into a number of different system development models, iterative being the most common but they also include waterfall, spiral and chaos models. They all encompass the full project life cycle. Common software development methodologies include Agile/Scrum, Structured Systems Analysis and Design Method (SSADM) and Microsoft Solutions Framework (MSF). Each step in a systems life cycle can be broken down into many smaller sub-steps or processes. Each stage follows logically after the previous, but it is an oversimplification to say that one stage is a distinct step after another. It is important to understand that the system lifecycle is iterative as well as the stages involved along the way. Different methodologies will have different variations of this lifecycle model. A common iterative lifecycle is show in the diagram below and each stage is described after the diagram. Stages of a system life cycle

1. Initial Idea
2. Feasibility Study
3. Requirements Analysis
4. Systems Analysis and Specification
5. Systems Design
6. Development
7. Testing
8. Implementation
9. Maintenance and Review
Initial Idea
All projects must start with an initial idea. Usually this consists of a brief definition on what is the project all about, what is its purpose and what the project aims to accomplish. How will the success of the project be measured?

Feasibility Study
Expanding on the Initial Idea, the Feasibility Study involves drawing up the terms of reference, which state the objectives and scope of the project, how long it should take and how the results should be presented. The terms of reference are usually drawn up by senior management. The feasibility study must determine if development of the project is justified in terms of economic and organisational terms. The main role of the analyst in the feasibility study is to analyse the current system at a high level. Data Flow Diagrams (DFD) are used to describe how the current system performs and to illustrate known problems. Feasibility studies are not carried out for all projects, and smaller projects omit this stage.

Requirements Analysis
The Requirements Analysis stage defines a series of possible solutions to the problem and presents them to management in terms of business options. These options may be supported by technical documents such as high-level DFD’s, Logical Data Models (LDM) and Work Practise Models. The requirements analysis report must also contain financial and risk assessments to be presented and supported by outline implementation descriptions. The steps involved within the requirements analysis will define the flow of data in the system, deriving system functions and to develop user role specifications, prototypes and process specifications.

Systems Analysis and Specification
The Systems Analysis stage is an extension to the feasibility study. If the project has a feasibility study then the bulk of the work has already been done. A terms of reference will also be required if one does not exist. The output from this stage is the System Specification which gives precise details of what the new system is required to do, but does not go into how it does it. It provides a logical model of the new system. Once agreed, the specification is the basis for the work done by the system designers.

Systems Design
This stage deals with how the requirements of the new system are carried out (how the logical model is implemented as a physical system). The system designer will develop a number of design options and test them against the requirements specification and design criteria. The one that comes closest to the design brief with the most cost effective use of equipment and personnel is selected and broken down into more detailed specs. Because of this the design stage has two phases: produce outline designs based on requirements specification with input from users and the detailed designs produced from the selected design.

Development
This is the only stage in the development where program code is written. The designs and specifications provide enough detail for the programmer to code and test individual modules. Each unit is tested to ensure that it meets the requirements of the specification.

Testing
Within the life cycle there are various levels of testing as well as the unit testing performed in the development stage. Link testing ensures that programs work together, e.g. the data passed from one program to another has the correct format. System testing ensures that the system as a whole performs according to the design specification. Recovery procedures must be tested as well as normal operation procedures. Finally user acceptance testing is carried out by the users in stages to ensure that the system is usable. Any modifications are passed back to the design stage where changes are made as necessary and passed to the development team.

Implementation
When the testing has been carried out to the users satisfaction the system, or parts of it, are put live. The “put live” phase can also be known as implementation, cut over or production. This is when the users start using the system to carry out their business activities.
There are two main approaches to implementation a project:
 Phased: Stand-alone subsets of the system are implemented over a period of time.
 Big Bang: The whole system is put live in one go.
Some systems will require special programs or tasks to convert existing data to a format usable by the new system. The process of changing data from the old system to the new is called conversion.

Maintenance and Review
Once the system is put into place, maintenance is required to ensure satisfactory operation. Maintenance should include regular reviews and evaluations to ensure that it is achieving its objectives, identify any aspects that can be improved or any operational problems. Maintenance falls into two categories, implementation of new features or elimination of errors.