ASP.

NET Review
Class
HTML is client side
Easy way to communicate with server
CSS is applicable in ASP.NET
JavaScript is not applicable in ASP.NET
ASP.NET is used to create webpage
Nowadays people are changing from ASP.NET to MVC
When ASP.NET is created they are called web forms and they have extension of
.aspx
The difference between HTML and ASP.NET
HTML is Client side,
ASP.NET is Server side
ASP.NET is whatever the client do you can monitor or save temporarily in the
system
State Management is different types of techniques which is used to maintain
state of the ASP.NET web form, but in HTML you cannot maintain state of the HTML
Statement management with the help of
Cookies,
A computer cookie is a small file no larger than four kilobytes used by Web
sites to log visitors to and from the site. Web sites download a cookie that collects
and stores information for use later.
View State The view state is the state of the page and all its controls. It is
automatically maintained across posts by ASP.NET framework.
Loading slow down can be avoided
ASP.NET server controls retain its state but HTML controls doesnt retain
its state
, Session
A computer cookie is a small file no larger than four kilobytes used by Web sites
to log visitors to and from the site. Web sites download a cookie that collects and
stores information for use later.
ASP.NET has ists own controls, ASP.NET is an event driven programing language
ASP.NET is event driven language means In computer programming, eventdriven programming is a programming paradigm in which the flow of the program

is determined by events such as user actions (mouse clicks, key presses), sensor
outputs, or messages from other programs/threads.
Initial page load:Post Back:-means when you reload the same page again and again

State Management and ASP.NET page Life Cycle

Session State:ASP.Net Application level
At the Application level (Application start)
Page level (Example: page load)
Control level (Example button click)
Session state is generally used for storing application data such as inventory,
supplier
list, customer record, or shopping cart. It can also keep information about the user
and his preferences, and keep the track of pending operations.
Session Mode
Third Server
SQL Server whatever it will be stored in the data base, SQL server can be used
the only problem of this is when we request
As soon as you login to the web application get stored in to session object, once
you log out from the web application the session deletes the login data from the
memory
How do Hackers use the weak side of a session:-if the session is not properly
done hackers can access the webpage without login to the system, generally
session is very important to secure your web application?
Web Form:- is a collection of web servers were the servers are designed to provide
service for any request send to the web form based on the condition of the network,
if a request is made to a busy server in the web form another server with in the web
form provides service to the request.
Load balancing is in case of one server is busy you another server provides
service to the request
Virtualization

ASP.NET Page Life Cycle

Web Server

Page Init (Page Initialization):-During Page Init All the ASP.NET

controllers get initialize and the View State generates some 1.4bit
encryption, it add some encrypted text that will be putted in to the view state
Pase Load: - During Page Load it assign any value to your
Page Render:Page Unload:-

State Management and ASP.NET page Life Cycle are the two important terms
which are common in ASP.NET job interview
ASP.NET Page Life Cycle
When a page is requested, it is loaded into the server memory, processed, and
sent to the browser. Then it is unloaded from the memory. At each of these steps,
methods and events are available, which could be overridden according to the
need of the application. In other words, you can write your own code to override
the default code.
The Page class creates a hierarchical tree of all the controls on the page. All the
components on the page, except the directives, are part of this control tree. You
can see the control tree by adding trace= "true" to the page directive. We will
cover page directives and tracing under 'directives' and 'event handling'.
The page life cycle phases are:

Initialization

Instantiation of the controls on the page

Restoration and maintenance of the state

Execution of the event handler codes

Page rendering

Understanding the page cycle helps in writing codes for making some specific
thing happen at any stage of the page life cycle. It also helps in writing custom
controls and initializing them at right time, populate their properties with viewstate data and run control behavior code.
Following are the different stages of an ASP.NET page:

Page request - When ASP.NET gets a page request, it decides whether to

parse and compile the page, or there would be a cached version of the
page; accordingly the response is sent.

Starting of page life cycle - At this stage, the Request and Response
objects are set. If the request is an old request or post back, the IsPostBack
property of the page is set to true. The Culture property of the page is also
set.

Page initialization - At this stage, the controls on the page are assigned
unique ID by setting the UniqueID property and the themes are applied. For
a new request, postback data is loaded and the control properties are
restored to the view-state values.

Page load - At this stage, control properties are set using the view state and
control state values.

Validation - Validate method of the validation control is called and on its

successful execution, the IsValid property of the page is set to true.

Postback event handling - If the request is a postback (old request), the

related event handler is invoked.

Page rendering - At this stage, view state for the page and all controls are
saved. The page calls the Render method for each control and the output of
rendering is written to the Output Stream class of the Response property of
page.

Unload - The rendered page is sent to the client and page properties, such
as Response and Request, are unloaded and all cleanup done.

ASP.NET Page Life Cycle Events

At each stage of the page life cycle, the page raises some events, which could be
coded. An event handler is basically a function or subroutine, bound to the event,
using declarative attributes such as On click or handle.
Following are the page life cycle events:

PreInit - PreInit is the first event in page life cycle. It checks the IsPostBack
property and determines whether the page is a postback. It sets the themes
and master pages, creates dynamic controls, and gets and sets profile
property values. This event can be handled by overloading the OnPreInit
method or creating a Page_PreInit handler.

Init - Init event initializes the control property and the control tree is built.
This event can be handled by overloading the OnInit method or creating a
Page_Init handler.

InitComplete - InitComplete event allows tracking of view state. All the

controls turn on view-state tracking.

LoadViewState -

LoadViewState

event

allows

loading

view

state

information into the controls.

LoadPostData - During this phase, the contents of all the input fields are
defined with the <form> tag are processed.

PreLoad - PreLoad occurs before the post back data is loaded in the
controls. This event can be handled by overloading the OnPreLoad method
or creating a Page_PreLoad handler.

Load - The Load event is raised for the page first and then recursively for all
child controls. The controls in the control tree are created. This event can be
handled by overloading the unloads method or creating a Page Load
handler.

Load Complete - The loading process is completed, control event handlers

are run, and page validation takes place. This event can be handled by
overloading the OnLoadComplete method or creating a Page_LoadComplete
handler

Pretender - The PreRender event occurs just before the output is rendered.
By handling this event, pages and controls can perform any updates before
the output is rendered.

PreRenderComplete - As the PreRender event is recursively fired for all

child controls, this event ensures the completion of the pre-rendering phase.

SaveStateComplete -

State

of

control

on

the

page

is

saved.

Personalization, control state and view state information is saved. The HTML
markup is generated. This stage can be handled by overriding the Render
method or creating a Page_Render handler.

UnLoad - The UnLoad phase is the last phase of the page life cycle. It raises
the UnLoad event for all controls recursively and lastly for the page itself.
Final cleanup is done and all resources and references, such as database
connections, are freed. This event can be handled by modifying the
OnUnLoad method or creating a Page_UnLoad handle

When class have only property it is called model class

Business layer can be replaced by the service layer or there is

Connection String

If you are using SQL Server Authentication you should use user name and
pass word for the Web.Config, but if we use on integrated security is used for a
Desktop server Authentication.

Get Property and set property

MARKETING SESSION
Things that should be done or Not
# Remove your resume from any job search site immediately
# deactivate/ purge your LinkedIn profile immediately
# Make your Facebook Profile PRIVATE or FRIENDS ONLY
# Make any other social media profiles private as well
# Contact your Recruiter or more at analysis if help is needed
# Sample resumes will be provided

# Once you have your resume pleas Lay-Out Detailed attention to

typography
# proofread each line till you are convinced
# Show your resume to your trainer or recruiter
# Must prepare companion stories of your resume
# keep all your resumes correctly labeled and double check before
submitting. (However dont save your resumes as
JohndoeHealthcareResume.doc or JohndoeFinanceVersion1)
MARKETING BRIEFING
Marketing is from 9:00AM to 9:00PM, and any one should be available
on this time interval
Accept Gtalk request sent by Marketers
Respond to marketers ASAP or within 1 hour of the requirement being sent
If possible always contact marketers by phone then by email
Always call Marketers for follow up when you send your resume
Always ask the Marketers- their name the name of the end-client, name of
the vendor, Vendor Company. This will avoid double submissions.
Vendor call can take place as early as 15 -30 minutes after resume
submission
Never miss a vendor call
If you miss, call back immediately or contact your marketer
Prepare an Excel sheet to keep track of all submissions. Include information
like submission, date, marketer name, phone, vendor name, phone, endclient name, resume version etc.
Taking vendor call Vendor will ask basic, screening questions-Tell me about
your current project? Have you worked on these tools? What is your work
status? Have you worked on those tools? What is your work status? Can you
provide reference?

MARKETING PROCESS
CONSULTANT-----MARKETER-------VENDOR---------END-CLIENT

List of Marketing Companies:Xceltech

Enterprise Business Solutions
InfoSpan
Synchronisys
ConceptsIT
Techligent
BIS (Business Intelligence Solutions)
Meritek