AlwaysVisibleExtender Control is used for visible always something
on web page either you scroll up and
down or left to right.
<%@
Page Language="C#" AutoEventWireup="true" CodeFile="AlwaysVisibleExtender.aspx.cs" Inherits="Ajax_AlwaysVisibleExtender"
%>
<%@
Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit"
TagPrefix="cc1"
%>
<!DOCTYPE html PUBLIC "-//W3C//DTD
XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
<title></title>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager>
<table>
<tr>
<td>
<div style="width:462px">
ASP.NET is a server-side
technology for building web applications. Almost all the work
happens on the web server and not the web browser. Whenever you
perform an action in
an ASP.NET page—such as clicking a button or sorting a GridView—the
entire page must
be posted back to the web server. Any significant action on a page
results in a postback.
If you think about it, this is incredibly inefficient. When you
perform a postback in an
ASP.NET page, the entire page must be transported across the Internet
from browser to
server. Next, the .NET class that corresponds to the page must
re-render the entire page
again from scratch. Finally, the finished page must be sent back
across the Internet to the
browser. This whole long, slow, agonizing process must occur even if
you are updating a
tiny section of the page. <br /><br />
Using a server-side technology such as ASP.NET results in a bad user
experience. Every
time a user performs some action on a page, the universe temporarily
freezes. Whenever
you perform a postback, the browser locks, the page jumps, and the
user must wait
patiently twiddling his thumbs while the page gets reconstructed. All
of us have grown
accustomed to this awful user experience. However, we would never
design our desktop
applications in the same way.<br /><br />
ASP.NET is a server-side technology for building web applications.
Almost all the work
happens on the web server and not the web browser. Whenever you
perform an action in
an ASP.NET page—such as clicking a button or sorting a GridView—the
entire page must
be posted back to the web server. Any significant action on a page
results in a postback.
If you think about it, this is incredibly inefficient. When you
perform a postback in an
ASP.NET page, the entire page must be transported across the Internet
from browser to
server. Next, the .NET class that corresponds to the page must
re-render the entire page
again from scratch. Finally, the finished page must be sent back
across the Internet to the
browser. This whole long, slow, agonizing process must occur even if
you are updating a
tiny section of the page.<br /><br />
Using a server-side technology such as ASP.NET results in a bad user
experience. Every
time a user performs some action on a page, the universe temporarily
freezes. Whenever
you perform a postback, the browser locks, the page jumps, and the
user must wait
patiently twiddling his thumbs while the page gets reconstructed. All
of us have grown
accustomed to this awful user experience. However, we would never
design our desktop
applications in the same way.<br /><br />
ASP.NET is a server-side technology for building web applications.
Almost all the work
happens on the web server and not the web browser. Whenever you
perform an action in
an ASP.NET page—such as clicking a button or sorting a GridView—the
entire page must
be posted back to the web server. Any significant action on a page
results in a postback.
If you think about it, this is incredibly inefficient. When you
perform a postback in an
ASP.NET page, the entire page must be transported across the Internet
from browser to
server. Next, the .NET class that corresponds to the page must
re-render the entire page
again from scratch. Finally, the finished page must be sent back
across the Internet to the
browser. This whole long, slow, agonizing process must occur even if
you are updating a
tiny section of the page.<br /><br />
Using a server-side technology such as ASP.NET results in a bad user
experience. Every
time a user performs some action on a page, the universe temporarily
freezes. Whenever
you perform a postback, the browser locks, the page jumps, and the
user must wait
patiently twiddling his thumbs while the page gets reconstructed. All
of us have grown
accustomed to this awful user experience. However, we would never
design our desktop
applications in the same way.
</div>
</td>
<td valign="top">
<div>
<asp:Panel ID="Panel1" runat="server" Width="372px" Height="202px"
BackColor="#CCFF66" >
<asp:Label ID="alabel1" runat="server" Text="Created By AspMaterials"
Font-Bold="True"
ForeColor="#0000CC"
></asp:Label><br />
<asp:Image ID="Image1" runat="server" ImageUrl="~/Ajax/Capture.PNG" Height="168px"
Width="181px" />
</asp:Panel>
<cc1:AlwaysVisibleControlExtender ID="AlwaysVisibleControlExtender1"
runat="server"
TargetControlID="Panel1"
VerticalSide="Top"
VerticalOffset="10"
HorizontalSide="Right"
HorizontalOffset="10"
ScrollEffectDuration="1.0"></cc1:AlwaysVisibleControlExtender>
</div>
</td>
</tr>
</table>
</div>
</form>
</body>
</html>
Run the code and see the output.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.