PowerWEB LiveControls for ASP.NET
from $499.00Available Platforms
A suite of 21 ASP.NET web server controls that add AJAX callback capabilities to your ASP.NET web applications. Lose the annoying flicker when posting data to the server!
The LiveControls Toolkit is a direct replacement for many standard Microsoft controls. Raise server-side callbacks and update form elements without disrupting the user experience with a page refresh. Includes code examples, samples and a tutorial.
Compare to Microsoft ASP.NET AJAX Technology:
Imagine the Possibilities...
- Shopping sites that dynamically update using server resources
- Financial applications that update rates without flickering
- Sports applications that update scores in real time
- Auction sites that countdown with superior Windows-like effects
Easy To Use
- Ajax-style callbacks manifest as familiar events
- Manipulate and update page elements client-side without reloading the page
- 100% DHTML generation
- No Java applets, Flash, JavaScript, plug-ins or ActiveX controls required
- Simplifed code maintenance with no JavaScript debugging
- Additional mouse, key and click events raised as server-side callbacks
Versatility
- Increase performance and reduce bandwidth with optimized ViewState management
- Play audio files server-side with LiveSound
- Raise events from captured keystrokes
- Client automatically updated when data is bound to the grid and list controls
- Poll the server at any time interval with LiveTimer
- Display alert, confirm and response MessageBoxes in server-side code
Flexibility
- Blocking and non-blocking options on the client
- Hook client events to server-side callbacks with the LiveCallback control
- Graceful degradation to standard ASP.NET postbacks in non-supported browsers
- Supports IE 6.0+ and Mozilla 1.3+ (Firefox, Netscape) for both PC and Mac
- Fully compatible with Visual Studio .NET 2005, 2008, 2010, 2012
- Many ASP.NET sample pages for both C# and VB.NET
LiveControls for ASP.NET's sample projects >
LiveControls for ASP.NET includes the following server controls:
LiveButton
Use the LiveButton control to create a push button on the Web page. You can create either a submit button or a command button.
LiveCallback
Use the LiveCallback to create custom callbacks into code-behind.
LiveCheckBox
Use the LiveCheckBox control to allow the user to select a true or false state.
LiveCheckBoxList
The LiveCheckBoxList control provides a multi selection check box group that can be dynamically generated with data binding. It contains an Items collection with members corresponding to individual items in the list.
LiveDataGrid
Use the LiveDataGrid control to display the fields of a data source as columns in a table dynamically. Each row in the LiveDataGrid control represents a record in the data source. The LiveDataGrid control supports selection, editing, deleting, paging, and sorting.
LiveDropDownList
Use the LiveDropDownList control to create a single selection drop-down list control.
LiveHyperlink
Use the LiveHyperLink control to create a link to another Web page.
LiveImage
Use the LiveImage control to display an image on the Web page.
LiveImageButton
Use the LiveImageButton control to display an image that responds to mouse clicks.
LiveLabel
Use the LiveLabel control to display text in a set location on the page.
LiveLinkButton
Use the LiveLinkButton control to create a hyperlink style button on the Web page.
LiveListBox
Use the LiveListBox control to create a list control that allows single or multiple item selection.
LiveMessageBox
Use LiveMessageBox to inform the user, ask the user for confirmation, or prompt the user for information.
LivePanel
Use the LivePanel control as a container for other controls.
LivePlaceHolder
Use the LivePlaceHolder control as a container to store dynamically added server controls to the Web page. The LivePlaceHolder control does not produce any visible output and is only used as a container for other controls on the Web page.
LiveRadioButton
The LiveRadioButton server control permits you to intersperse the radio buttons in a group with other content in the page.
LiveRadioButtonList
The LiveRadioButtonList control provides page developers with a single-selection radio button group that can be dynamically generated through data binding.
LiveSound
Use LiveSound to play a sound file client-side during a callback.
LiveTextBox
Use LiveTextBox to display a text box control for user input.
LiveTimer
Use LiveTimer to raise an event at user-defined intervals, enabling server polling.
LiveWrapper
Use LiveWrapper to isolate 3rd-party controls for precise rendering.
Environments
PowerWEB LiveControls for ASP.NET will operate on any Microsoft operating system that fully supports the Microsoft .NET Framework 2.0, 3.5, 4.0 and 4.5, as by nature, .NET components are dependent on the Framework rather than a specific operating system. The components can be used with any .NET compliant language, but have only undergone testing with the following languages:
- C#
- VB.NET
PowerWEB LiveControls for ASP.NET components have been tested in the following development environments:
- Visual Studio .NET 2005, 2008, 2010, 2012
- Visual Web Developer Express
Browser Support
PowerWEB Live Controls for ASP.NET supports all modern browsers with JavaScript enabled and that comply with RFC 1867, but has specifically been designed for and tested with:
- Microsoft Internet Explorer 6, 7, 8 and 9.
- All versions of Firefox for Windows and Mac OS
- All versions of Google Chrome
- Safari for Windows and Mac OS
LiveControls for ASP.NET includes the following C# and VB.NET sample applications:
LiveSudoku
A fully-functional Sudoku puzzle game that demonstrates how LiveControls can be used to create menus and to dynamically alter application look and feel.
LiveAuction
Demonstrates using LiveControls to update an imaginary auction for a guitar in real-time.
LiveProgress
Demonstrates using LiveControls to the update a progress bar based on information from the server.
LiveComparison
Compares the difference between using LiveControls and standard Microsoft controls.
LiveShoppingCart
Demonstrates a shopping cart that can be updated with real-time server price information as options are chosen without a postback.
LiveSlideShow
Demonstrates a slideshow that is driven by server-side image URLs.
LiveTutorial
Demonstrates how the PowerWEB LiveControls for ASP.NET can be used and explains the technology.
Download all the LiveControls Samples Now!
Product Release History
The following is a list of public releases for all components shipped with PowerWEB LiveControls for ASP.NET (Latest Release 2015-12-22)
PowerWEB LiveControls for ASP.NET
Current Version: 4.0.4.0
4.0.4.0 Released: 2015-12-22
Product fixes in this release:
- A JavaScript injection vulnerability has been closed. (725)
4.0.3.1 Released: 2013-12-26
Product fixes in this release:
- Resolved an issue where LiveListBox, LiveDropdownList, and LiveRadioButtonList would sometimes fail to post changes back to the client. (TFS247)
- The footer of the LiveDataGrid control should now render correctly when it is displayed. (TFS248)
4.0.2.2 Released: 2012-10-31
- Updated for Visual Studio 2012 integration and Windows 8 compatibility.
- Trial licensing operation updated.
Product fixes in this release:
- Addressed a globalization issue that prevented correct operation for systems using the following language cultures: Azeri (az), Azeri-Latin (az-Latn), Azeri-Latin-Azerbaijan (az-Latn-AZ), Turkish (tr), Turkish-Turkey (tr-TR). (TFS31)
4.0.1.1 Released: 2012-07-12
Product fixes in this release:
- Fixed a licensing issue with web service applications.
- Updated the title bar of licensing messages to not indicate a product is in trial when it is licensed.
4.0.0.3 Released: 2012-07-05
- Licensing has been upgraded to the 4.0 model. There are no longer separate "trial" and "licensed" versions of the dll.
Product fixes in this release:
- LiveDataGridItems now have unique ClientIDs in Framework 4.0, fixing row selection problems.
- LiveCheckBox and LiveRadioButton now function in Framework 4.0. (5320)
1.6.3.0 Released: 2009-09-09
Product fixes in this release:
- Addressed problem where ForceSSL was not forcing all links to be secure.
- Fixed problem when ImageUrls were set using backslashes in the path. (3651)
- LiveCheckBoxColumn now correctly reports the value of its Checked property. (4533)
- WaitMessage now works correctly for LiveDataGrid. (4882)
- Fixed problem with Firefox when ViewStateCache was not used. (4978, 4569)
- Fixed problem with LiveDataGrid when DataSource was set at design time. (4996)
1.6.2.0 Released: 2008-08-28
- This release corrects an issue introduced with .NET Framework 3.5 Service Pack 1. No other corrections or enhancements are added with this release, and upgrading is unnecessary unless using on a workstation with SP1.
Considering Microsoft ASP.NET AJAX?
Microsoft ASP.NET AJAX (formerly named Atlas) is a high-quality Ajax platform for ASP.NET developers. Before investing time and money integrating it into your next project, consider the following features unique to PowerWEB LiveControls:
- Support for all ASP.NET versions – 1.0, 1.1, and 2.0
- Compact and efficient communication including ViewState caching
- Extended client-side event support
- Multiple, simultaneous callbacks supported
- Easily customizable
- Multiple degradation technologies supported
- Ease of application conceptualization
Support for all ASP.NET versions – 1.0, 1.1, and 2.0
Taking advantage of Ajax rich-client functionality does not mean that you need to upgrade to ASP.NET 2.0. PowerWEB LiveControls has been compatible with all available versions of ASP.NET since it was released in 2004. Whether you are planning on upgrading to ASP.NET 2.0, or you are building applications in a mixed-platform environment, LiveControls provides the same user interface enhancements.
Compact and efficient communication including ViewState caching
PowerWEB LiveControls was not only engineered to improve web user interfaces, but to increase ASP.NET web application performance. In typical Ajax implementations including ASP.NET AJAX, page-level elements are modified by rebuilding and transmitting all HTML markup for each affected element. LiveControls transmits only the code necessary to update modified elements and even sub-element attributes.
For example, if a page contains a DataGrid comprised of 10 columns and 10 rows, a typical Ajax implementation would transmit the entire HTML table and replace it, even if a single string in a single cell was modified. By comparison, LiveControls only transmits the code required to update the single string.
% Changed | 1% | 10% | 25% | 50% | 100% |
---|---|---|---|---|---|
LiveControls | 55 bytes | 550 bytes | 1375 bytes | 2750 bytes | 5500 bytes |
ASP.NET AJAX | 5702 bytes | 5702 bytes | 5702 bytes | 5702 bytes | 5702 bytes |
Additionally, LiveControls uses a configurable system for caching ViewState. This greatly reduces the amount of data passed between client and server for each operation. Not only do these features dramatically reduce bandwidth costs, they make for more responsive applications.
Extended client-side event support
PowerWEB LiveControls provides you with the ability to trap many client-side events not available in other Ajax implementations. Events such as MouseOver, KeyPressed, DoubleClick and more are raised as server events using the same ASP.NET code-behind model.
Multiple, simultaneous callbacks supported
LiveControls supports an unlimited number of simultaneous callbacks. With ASP.NET AJAX, if two or more simultaneous callbacks occur, only one is processed. Although the scenarios are limited where this would occur, critical events and data may be lost if it does. LiveControls processes and responds to all callbacks issued from the client.
Easily customizable
Included with PowerWEB LiveControls are client and server APIs as well as a LiveCallback control. This makes it possible to use LiveControls to integrate with other Ajax libraries, platforms and vendor controls. The APIs provide client-side pre- and post-callback events, and the LiveCallback exposes the full LiveControls callback communication framework so you may execute your own server methods without a full page post.
Multiple degradation technologies supported
Graceful degradation is the ability for a given technology to adjust itself to the capabilities found in its operating environment. For web user interfaces, this is important because of the prevalence of multiple browser types, versions, and security configurations. An Ajax implementation should attempt to use XmlHttpRequest for issuing callbacks, then ‘degrade’ to other technologies to limit user disruptions if it is not available in the client. Microsoft ASP.NET AJAX supports XmlHttpRequest, IFRAME, and finally resorts to using full page PostBacks. LiveControls supports XmlHttpRequest, Flash communications, IFRAME, and PostBack. As the second fallback mechanism, Flash is a better option than IFRAME, as it offers less UI disruption. In addition, Flash exhibits the same performance in all modern browsers, unlike IFRAME which can behave differently or not at all under many browser configurations.
Ease of application conceptualization
A typical ASP.NET AJAX implementation utilizes the UpdatePanel approach, which is somewhat non-intuitive for most ASP.NET application architects, especially in terms of optimization. For example, if your WebForm contains many different controls, you may be tempted to wrap the lot in a single UpdatePanel. However, doing so would impact communications because all elements in the UpdatePanel would be redrawn in each callback. In order to optimize the application, several UpdatePanels would be used to group related UI components, possibly even one per control. The benefit of using LiveControls is that you need not modify your interface design and conceptualization. LiveControls are used like standard ASP.NET controls, and the communications optimization is handled internally.
Ajax Button Control
LiveButton ASP.NET Server Control Information
LiveLinkButton ASP.NET Server Control Information
LiveImageButton ASP.NET Server Control Information
This page includes information about the LiveButton, LiveLinkButton, and LiveImageButton Server Controls, which are included in PowerWEB LiveControls for ASP.NET:
(Note. All of the following references to LiveButton apply equally to LiveLinkButton and LiveImageButton).
The LiveButton server control initiates a remote-scripted callback, raising the Click event on the server. Within this event, modify any UI element, and the visual update occurs on the browser without refreshing the entire page.
Remember! Any LiveControl which raises a callback to the server (such as LiveButton, LiveImageButton, and LiveLinkButton) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveButton control has the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Uses same interface as the standard ASP.NET Button, so there is no learning curve.
- Adds a LocationClick event which provides the X and Y coordinates of the mouse-click.
- Use with LiveDataGrid to display a column of buttons in a table that can be used to select, edit, modify, or delete the items in the row.
- Use the Blocking property to cause button is disabled when clicked (and re-enabled when the callback completes) to keep the user from double-clicking the button before the request completes.
- Use in conjunction with a WaitElement to display a message (such as "Processing...") while the callback is pending.
- LiveLinkButton performs the same tasks as LiveButton but presents an HTML hyperlink instead of an HTML button.
- LiveImageButton performs the same tasks as LiveButton but presents an HTML image instead of an HTML button.
Some example uses for LiveButton:
- Use in place of ANY standard ASP.NET button to replace the standard postback with a much "smoother" callback.
- Use the X and Y mouse coordinates available in the LocationClick event to display a popup panel at the location of the mouse click.
- Use anywhere you need to send data to the server (and update the client) without refreshing the page.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveButton, LiveLinkButton, and LiveImageButton.
<cc1:LiveButton id="LiveButton1" runat="server" Text="My Button"></cc1:LiveButton>
<cc1:LiveLinkButton id="LiveLinkButton1" runat="server" Text="MyLinkButton"></cc1:LiveButton>
<cc1:LiveButton id="LiveImageButton1" runat="server" ImageUrl="myimg.gif"></cc1:LiveButton>
Code-Behind Example
This demonstrates handling the LiveButton.Click event
// Click event is raised when the button is clicked.
private void LiveButton1_Click(object sender, System.EventArgs e)
{
LiveLabel1.Text = DateTime.Now.ToLongTimeString();
LiveCallback ASP.NET Server Control Information
This page includes information about the LiveCallback Server Control, which is included in PowerWEB LiveControls for ASP.NET:
While remote-scripting functionality required by most web applications is encapsulated by the other controls included with LiveControls for ASP.NET, there are times when a more custom callback is required. For these purposes, the LiveCallback control is used. The LiveCallback control is used to call a server function (and get the return value from the function) from the browser without refreshing the page. Simply drag a LiveCallback control on a webform, create the server function to call, then call the client-side "pwBeginCallServerFunction" function and a callback is transparently sent to the server, calling the function, and returning the value to the client.
Remember! Any LiveControl which raises a callback to the server (such as LiveCallback) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveCallback control has the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- From client-side script, call a server function without refreshing the page.
- Pass up to 9 parameters into the server function.
- Operates as a transparent, background operation.
Some example uses for LiveCallback:
- Pass data transparently to the server as needed.
- Create a text "autosave" feature which works in the background while the user fills out a textbox.
- Create custom your own custom LiveControls by wiring a server-side function to a client-side event.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following code demonstrates the server tags and JavaScript required to call a server function.
<script language="javascript">
function doCallback(){
function clientFunction(response){
</script>
<input type="button" value="Click me" onclick="doCallback()">
<cc1:LiveCallback id="LiveCallback1" runat="server"></cc1:LiveCallback>
Code-Behind Example
This code demonstrates an example server function to call from the client-side.
public string ServerFunction()
{
LivePlaceHolder ASP.NET Server Control Information
This page includes information about the LivePlaceHolder Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LivePlaceHolder control contained with the LiveControls for ASP.NET suite displays dynamically created WebControls on the browser without refreshing the page.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for a LivePlaceHolder control
<cc1:LivePlaceHolder id="LivePlaceHolder1" runat="server"></cc1:LivePlaceHolder>
Code-Behind Example
The following code demonstrates dynamically adding a control to the LivePlaceHolder in a button click event.
private void LiveButton1_Click(object sender, System.EventArgs e)
{
LiveLabel label = new LiveLabel();
label.ID = "mylabel";
label.Text = "Hello World";
label.BackColor = Color.Red;
// Add it to the PlaceHolder. It will be displayed in the browser without refreshing the page
LivePlaceHolder1.Controls.Add(label);
CheckBox, RadioButton, CheckBoxList, RadioButtonList
LiveCheckBox ASP.NET Server Control Information
LiveRadioButton ASP.NET Server Control Information
LiveCheckBoxList ASP.NET Server Control Information
LiveRadioButtonList ASP.NET Server Control Information
This page includes information about the LiveCheckBox, LiveRadioButton, LiveCheckBoxList, and LiveRadioButtonList Server Controls, which are included in PowerWEB LiveControls for ASP.NET:
The LiveCheckBox server control (representing an HTML checkbox) and the LiveRadioButton server control (representing an HTML radio button) make it possible to communicate with a webserver and update client-side elements when either of these elements are clicked, without "refreshing" the page.
The "list" versions of these controls (LiveCheckBoxList and LiveRadioButtonList) are server controls which can be bound to a datasource, producing multiple instances of checkboxes and radio buttons which can raise callbacks to the server.
Remember! Any LiveControl which raises a callback to the server (such as LiveCheckBox or LiveRadioButton) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveCheckBox and LiveRadioButton controls have the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Uses same interface as the standard ASP.NET CheckBox and RadioButton, so there is no learning curve.
- Use LiveRadioButton with LiveDataGrid to display a column of radio buttons which select the row when clicked.
- Use LiveCheckBox with LiveDataGrid to display a column of checkboxes which display (and allow editing of) boolean database data.
- Bind LiveRadioButtonList or LiveCheckBox list to a datasource to easily produce lists of "callback-enabled" checkboxes and radiobuttons.
Some example uses for LiveCheckBox and LiveRadioButton:
- Use in place of ANY standard ASP.NET CheckBox or RadioButton to replace the standard postback with a much "smoother" callback.
- Use anywhere you need to send data to the server (and update the client) without refreshing the page.
- Create a live "poll" which is updated in real-time without refreshing the browser.
- Create a web-quiz.
- Create a form for a configurable product (such as Dell's "configure your computer" form) which updates the price as various options are selected/deselected.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveCheckBox and LiveRadioButton.
<cc1:LiveCheckBox id="LiveCheckBox1" runat="server" AutoPostBack="True"></cc1:LiveCheckBox>
<cc1:LiveRadioButton id="LiveRadioButton1" runat="server" AutoPostBack="True"></cc1:LiveRadioButton>
Code-Behind Example
This demonstrates handling the LiveCheckBox.SelectedIndexChanged event
// SelectedIndexChanged event is raised when the LiveCheckBox is checked.
private void LiveCheckBox1_CheckedChanged(object sender, System.EventArgs e)
{
LiveDataGrid ASP.NET Server Control Information
This page includes information about the LiveDataGrid Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveDataGrid emulates the standard ASP.NET DataGrid features/functionality while replacing the standard postback with a remote-scripted callback, resulting in a highly-responsive grid which has the look, feel, and responsiveness of a Windows grid. When performing common grid functions such as sorting columns, selecting pages, selecting rows, etc, these operations are performed without a browser refresh, resulting in a very smooth, Windows-like execution. In addition, editing and updating grid data also occurs without refreshing the page, making data modification much more intuitive and responsive.
Remember! Any LiveControl which raises a callback to the server (such as LiveDataGrid) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveDataGrid control has the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Standard grid functions such as paging, sorting, editing, selecting, and updating occur using remote-scripting, resulting in lightning-quick data loading on the client-side.
- Row editing occurs without browser refresh.
- Bind data on postback and visual update occurs client-side without a refresh.
- Automatic support for displaying a column of radio buttons used to select rows.
- Automatic support for displaying a column of checkboxes used to display and modify boolean database data.
Some example uses for LiveDataGrid:
- Use in conjunction with other LiveControls to build web applications such as contact management, content management, email, etc which have a Windows look and feel.
- Use in conjunction with LiveTimer to display tabular data that requires real time updates (such as sports scores, stock info, weather, network data, etc).
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for a LiveDataGrid
<cc1:LiveDataGrid id="LiveDataGrid1" runat="server" AutoGenerateColumns="False">
<cc1:LiveBoundColumn DataField="ProductName" SortExpression="ProductName" HeaderText="Product Name"></cc1:LiveBoundColumn>
<cc1:LiveBoundColumn DataField="QuantityPerUnit" SortExpression="QuantityPerUnit" HeaderText="Quantity Per Unit"></cc1:LiveBoundColumn>
<cc1:LiveBoundColumn DataField="UnitsInStock" SortExpression="UnitsInStock" HeaderText="Units In Stock"></cc1:LiveBoundColumn>
<cc1:LiveButtonColumn Text="LiveButton" HeaderText="Live Buttons" CommandName="Blah"></cc1:LiveButtonColumn>
<cc1:LiveButtonColumn Text="Delete" HeaderText="Delete Buttons" CommandName="Delete"></cc1:LiveButtonColumn>
<cc1:LiveEditCommandColumn ButtonType="LinkButton" UpdateText="Update" HeaderText="Edit Buttons" CancelText="Cancel" EditText="Edit"></cc1:LiveEditCommandColumn>
<cc1:LiveCheckBoxColumn DataField="Discontinued" NonEditModeBehavior="DisabledCheckBox" AutoPostback="False"></cc1:LiveCheckBoxColumn>
Code-Behind Example
The following code demonstrates handling some typical DataGrid events.
private void LiveDataGrid1_CancelCommand(object source, System.Web.UI.WebControls.DataGridCommandEventArgs e)
{
private void LiveDataGrid1_EditCommand(object source, System.Web.UI.WebControls.DataGridCommandEventArgs e)
{
private void LiveDataGrid1_UpdateCommand(object source, System.Web.UI.WebControls.DataGridCommandEventArgs e)
{
LiveDataGrid1.EditItemIndex = -1;
LiveDropDownList and LiveListBox ASP.NET Server Control Information
This page includes information about the LiveDropDownList and LiveListBox Server Controls, which are included in PowerWEB LiveControls for ASP.NET:
The LiveDropDownList and LiveListBox (both of which represent an HTML SELECT element) server controls replace the standard ASP.NET DropDownList and ListBox server controls, using remote-scripted callback technology in place of postback technology. As a result, a user is able to select an item of these lists, raising a server-event, and update client-side elements without refreshing the browser. This enables the creation of web applications which have an unprecedented level of responsiveness.
Remember! Any LiveControl which raises a callback to the server (such as LiveButton, LiveImageButton, and LiveLinkButton) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveDropDownList and LiveListBox controls have the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Uses same interface as the standard ASP.NET DropDownList and ListBox , so there is no learning curve.
- Bind data on postback and visual update occurs client-side without a refresh.
Some example uses for LiveDropDownList and LiveListBox:
- Create a form for a configurable product (such as Dell's "configure your computer" form) which updates the price as various options are selected/deselected.
- Display heirachical data, displaying the items of the next node in a list as each parent node is selected.
- Use LiveDropDownList in conjunction with LiveDataGrid to display a column which contains a dropdown in each cell.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveButton, LiveLinkButton, and LiveImageButton.
<cc1:LiveDropDownList id="LiveDropDownList1" runat="server"></cc1:LiveDropDownList>
<cc1:LiveListBox id="LiveDropDownList1" runat="server"></cc1:LiveLiveBox>
Code-Behind Example
This demonstrates binding the LiveDropDownList and handling the LiveDropDownList.SelectedIndexChanged event.
// Bind some test data
ArrayList list1 = new ArrayList();
list1.Add("item 1");
list1.Add("item 2");
list1.Add("item 3");
list1.Add("item 4");
LiveDropDownList1.DataSource = list1;
LiveDropDownList1.DataBind();
// Handle SelectedIndexChanged event
private void LiveDropDownList1_SelectedIndexChanged(object sender, System.EventArgs e)
{
LiveHyperlink ASP.NET Server Control Information
This page includes information about the LiveHyperlink Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveHyperlink server control represents an HTML link which can be updated from within a remote-scripted callback without refreshing the browser.
Remember! Any LiveControl which raises a callback to the server (such as LiveTimer) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveHyperlink control has the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Uses the same interface as the standard ASP.NET HyperLink control.
- Dynamically change link targets/images based on current state of application. The interface is not changed, so this occurs without any disruption to the user's interaction with the page.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveHyperlink
<cc1:LiveHyperLink id="LiveHyperLink1" runat="server">Click Here</cc1:LiveHyperLink>
Code-Behind Example
The LiveHyperlink is also quite easy to use in Code-Behind.
// Dynamically change the url of the link.
LiveHyperLink1.NavigateUrl = "http://www.dart.com";
LiveImage ASP.NET Server Control Information
This page includes information about the LiveImage Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveImage server control represents an HTML image which can have it's src attribute changed (as well as other client-side properties) from within a remote-scripted callback without refreshing the browser.
Remember! Any LiveControl which raises a callback to the server (such as LiveTimer) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveImage control has the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Use the server MouseEnter, MouseLeave effects to create an image swap effect.
- Use in conjunction with the LiveTimer to create an automated slide show.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveImage
<cc1:LiveImage id="LiveImage1" runat="server" ImageUrl="myimg.gif"></cc1:LiveImage>
Code-Behind Example
The following code demonstrates using the MouseEnter and MouseLeave server events to make an image swap effect.
private void LiveImage1_MouseEnter(object sender, Dart.PowerWEB.LiveControls.LocationEventArgs e)
{
private void LiveImage1_MouseLeave(object sender, Dart.PowerWEB.LiveControls.LocationEventArgs e)
{
Ajax Button Control
LiveButton ASP.NET Server Control Information
LiveLinkButton ASP.NET Server Control Information
LiveImageButton ASP.NET Server Control Information
This page includes information about the LiveButton, LiveLinkButton, and LiveImageButton Server Controls, which are included in PowerWEB LiveControls for ASP.NET:
(Note. All of the following references to LiveButton apply equally to LiveLinkButton and LiveImageButton).
The LiveButton server control initiates a remote-scripted callback, raising the Click event on the server. Within this event, modify any UI element, and the visual update occurs on the browser without refreshing the entire page.
Remember! Any LiveControl which raises a callback to the server (such as LiveButton, LiveImageButton, and LiveLinkButton) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveButton control has the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Uses same interface as the standard ASP.NET Button, so there is no learning curve.
- Adds a LocationClick event which provides the X and Y coordinates of the mouse-click.
- Use with LiveDataGrid to display a column of buttons in a table that can be used to select, edit, modify, or delete the items in the row.
- Use the Blocking property to cause button is disabled when clicked (and re-enabled when the callback completes) to keep the user from double-clicking the button before the request completes.
- Use in conjunction with a WaitElement to display a message (such as "Processing...") while the callback is pending.
- LiveLinkButton performs the same tasks as LiveButton but presents an HTML hyperlink instead of an HTML button.
- LiveImageButton performs the same tasks as LiveButton but presents an HTML image instead of an HTML button.
Some example uses for LiveButton:
- Use in place of ANY standard ASP.NET button to replace the standard postback with a much "smoother" callback.
- Use the X and Y mouse coordinates available in the LocationClick event to display a popup panel at the location of the mouse click.
- Use anywhere you need to send data to the server (and update the client) without refreshing the page.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveButton, LiveLinkButton, and LiveImageButton.
<cc1:LiveButton id="LiveButton1" runat="server" Text="My Button"></cc1:LiveButton>
<cc1:LiveLinkButton id="LiveLinkButton1" runat="server" Text="MyLinkButton"></cc1:LiveButton>
<cc1:LiveButton id="LiveImageButton1" runat="server" ImageUrl="myimg.gif"></cc1:LiveButton>
Code-Behind Example
This demonstrates handling the LiveButton.Click event
// Click event is raised when the button is clicked.
private void LiveButton1_Click(object sender, System.EventArgs e)
{
// update a label with the current time
LiveLabel1.Text = DateTime.Now.ToLongTimeString();
}
LiveLabel ASP.NET Server Control Information
This page includes information about the LiveLabel Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveLabel server control represents an HTML SPAN element, and is useful in conjunction with the other controls included with LiveControls for ASP.NET as an all-purpose container for text and HTML. Simply drag a LiveLabel onto the form, drag another control on the form which raises a callback (such as a LiveButton), then manipulate the properties of the LiveLabel to perform many DHTML-style effects. Even though these properties are set on the server, since callback technology is used, the effects occur without a browser refresh.
- Set the Text property to a text string to dynamically change the text of the span.
- Set the Text property to an HTML string to dynamically insert an HTML element into the span.
- Set the Display property to do a show/hide effect.
- Use the X and Y coordinates of the LocationClick event to display the Label at a fixed location (for example, you could create a right-click popup using this technique).
- Change the background color, border color, or border style to notify some sort of state change.
- ...many more.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveLabel
<cc1:LiveLabel id="LiveLabel1" runat="server">Hello world</cc1:LiveLabel>
Code-Behind Example
The following code demonstrates using the MouseEnter and MouseLeave server events to change the background color of the label.
{
private void LiveLabel1_MouseLeave(object sender, Dart.PowerWEB.LiveControls.LocationEventArgs e)
{
LiveMessageBox ASP.NET Server Control Information
This page includes information about the LiveMessageBox Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveMessageBox is used to display a JavaScript alert (or prompt/confirm) to the user by using a server-side method. The alert box is displayed without any UI disruption to the user (the browser does not "refresh"). If prompt or confirm display types are used (these types require user input) when the data is received from the user, the response is sent transparently to the server, raising the Response event.
- Use DialogType.Alert to display a message to the user.
- Use DialogType.Confirm to display a message with a yes/no option to the user.
- Use DialogType.Prompt to display a message with a textbox, enabling the user to input some data.
- Use for transparent SERVER-SIDE form validation.
- Create a step by step wizard.
- Display error messages to the user.
Remember! Any LiveControl which raises a callback to the server (such as LiveMessageBox) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveLabel
<cc1:LiveMessageBox id="LiveMessageBox1" runat="server"></cc1:LiveMessageBox>
Code-Behind Example
The following code demonstrates using the MouseEnter and MouseLeave server events to change the background color of the label.
// Prompt the user for some info.
LiveMessageBox1.Show("Please enter something:", Dart.PowerWEB.LiveControls.DialogType.Prompt);
// Response received from client
private void LiveMessageBox1_Response(object sender, Dart.PowerWEB.LiveControls.ResponseEventArgs e)
{
LivePanel ASP.NET Server Control Information
This page includes information about the LivePanel Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LivePanel server control is essential for creating complex remote-scripted applications using LiveControls for ASP.NET. Since LiveControl applications are designed to operate without refreshing the entire page, this adds a bit of complexity to creating large scale web applications (such as web email applications, web contact management applications, web bug tracking applications, etc). LivePanel can be used to easily section your applications into different pages for use.
For example, if the application is a web based application, this could conceivably be made up of several "forms"...for example there could be a "login page", a "display mailbox contents page", a "compose page", a "configure account page", a "read email page", etc. One way you could design this application is to place the user interface of each "page" on a separate LivePanel on the same aspx page. Control which interface the user sees by changing the LivePanel.Display property to show the current interface and hiding the rest. Since these changes will be made using remote-scripting technology, the result will be an application with lightning quick response and no user interface disruption as the browser is not refreshed.
Browser Compatibility
LiveControls has been tested and is fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate server tag settings to two LivePanel controls containing child controls.
<cc1:LivePanel id="LivePanel1" runat="server">
<cc1:LiveTextBox id="LiveTextBox1" runat="server"></cc1:LiveTextBox>
<cc1:LiveButton id="LiveButton1" runat="server"></cc1:LiveButton>
<cc1:LivePanel id="LivePanel2" runat="server">
<cc1:LiveTextBox id="LiveTextbox2" runat="server"></cc1:LiveTextBox>
<cc1:LiveButton id="LiveButton2" runat="server"></cc1:LiveButton>
Code-Behind Example
The following code demonstrates hiding and showing panels to display different interfaces to the user.
private void LiveButton1_Click(object sender, System.EventArgs e)
{
LivePanel1.Display = false;
LivePanel2.Display = true;
private void LiveButton2_Click(object sender, System.EventArgs e)
{
LivePanel1.Display = true;
LivePanel2.Display = false;
Liveplaceholder ASP.NET Server Control Information
This page includes information about the LivePanel Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LivePanel server control is essential for creating complex remote-scripted applications using LiveControls for ASP.NET. Since LiveControl applications are designed to operate without refreshing the entire page, this adds a bit of complexity to creating large scale web applications (such as web email applications, web contact management applications, web bug tracking applications, etc). LivePanel can be used to easily section your applications into different pages for use.
For example, if the application is a web based application, this could conceivably be made up of several "forms"...for example there could be a "login page", a "display mailbox contents page", a "compose page", a "configure account page", a "read email page", etc. One way you could design this application is to place the user interface of each "page" on a separate LivePanel on the same aspx page. Control which interface the user sees by changing the LivePanel.Display property to show the current interface and hiding the rest. Since these changes will be made using remote-scripting technology, the result will be an application with lightning quick response and no user interface disruption as the browser is not refreshed.
Browser Compatibility
LiveControls has been tested and is fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate server tag settings to two LivePanel controls containing child controls.
<cc1:LivePanel id="LivePanel1" runat="server">
<cc1:LiveLabel id="LiveLabel1" runat="server">Panel 1 Displayed</cc1:LiveLabel>
<cc1:LiveTextBox id="LiveTextBox1" runat="server"></cc1:LiveTextBox>
<cc1:LiveButton id="LiveButton1" runat="server"></cc1:LiveButton>
</cc1:LivePanel>
<cc1:LivePanel id="LivePanel2" runat="server">
<cc1:LiveLabel id="LiveLabel2" runat="server">Panel 2 Displayed</cc1:LiveLabel>
<cc1:LiveTextBox id="LiveTextbox2" runat="server"></cc1:LiveTextBox>
<cc1:LiveButton id="LiveButton2" runat="server"></cc1:LiveButton>
</cc1:LivePanel>
Code-Behind Example
The following code demonstrates hiding and showing panels to display different interfaces to the user.
private void LiveButton1_Click(object sender, System.EventArgs e)
{
LivePanel1.Display = false;
LivePanel2.Display = true;
private void LiveButton2_Click(object sender, System.EventArgs e)
{
LivePanel1.Display = true;
LivePanel2.Display = false;
LiveSound ASP.NET Server Control Information
This page includes information about the LiveSound Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveSound server control has the ability to play a sound on a webpage from within a client remote scripted callback. This capability adds many new potential features to web application, for example:
- Play an alarm when a critical condition occurs in a web application. For example, if the web application is monitoring server traffic in real time, an alert can be played when the server becomes overloaded.
- Associate a sound effect with some user interface action. For example, if creating a chat application, a doorbell sound could be played when a new person enters the chat room, a chime could be played when a new message is received, etc.
- Associate a sound effect with an application state change. For example, an email application (such as Hotmail) could continually poll the server for new messages (using LiveTimer) and, when a new message is received, a sound could be played like Microsoft Outlook.
- Tie sound effects to button clicks, mouse actions, etc.
Browser Compatibility
LiveControls has been tested and is fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveSound with a sound file.
Code-Behind Example
The following code demonstrates playing a sound on a button click.
{
LiveTextBox ASP.NET Server Control Information
This page includes information about the LiveTextBox Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveTextBox server control enables the addition of advanced text input functionality into a webpage. The LiveTextBox control (like all LiveControls) replaces the standard ASP.NET postback approach with a remote scripted callback, allowing the textbox to send it's data to the server, and be updated from the server, without refreshing the page or disrupting the user's interactions with the page. This enables developers to build web applications with unprecedented response and fluidity. For example, to create a simple chat application, add a LiveTextBox (for the user to input their chat message), a LiveButton (for the user to send their chat message), and a LiveLabel (to display the chat room transcript) and write a few lines of server code tying the controls together. In addition, set the AutoPostBack property to true to have the LiveTextBox initiate the callback (when the user tabs out of the field) instead of the button. For another useful feature, implement the LiveTextBox.KeyDown event to have the LiveTextBox callback with it's new data on each key press.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing a LiveTextBox control.
<cc1:LiveTextBox id="LiveTextBox1" runat="server"></cc1:LiveTextBox>
Code-Behind Example
The following code demonstrates getting the text of the LiveTextBox and displaying the text on a label.
private void LiveButton1_Click(object sender, System.EventArgs e)
{
LiveTimer ASP.NET Server Control Information
This page includes information about the LiveTimer Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveTimer server control is used to periodically poll the server for new data. Set the Interval property and start the timer and a callback is issued to the server, raising the Timer.Tick event. Within this event, take whatever action you wish and update the client UI. All of this client/server communication occurs transparently, without any UI interruption or browser refresh. As a result, a static webpage can become "live": constantly and smoothly updated as new data is available on the server.
Remember! Any LiveControl which raises a callback to the server (such as LiveTimer) raises a server event within which ANY client-side element can be visually updated without refreshing the page!
The LiveTimer control has the following features:
- Cross-browser compatible, no plugins, downloads, or security warnings.
- Intuitive interface has Interval property and Start() and Stop() methods, exactly like Windows Timer.
- Set Interval property to 0 and the Tick event is raised as often as possible (as often as network bandwidth allows), ideal for applications that require data refreshes as close to "real-time" as possible.
- When used in browsers that don't allow remote scripting techniques, the ASP.NET __doPostBack function is called in place of the callback function to periodically issue a standard postback.
Some example uses for LiveTimer:
- Build a web-chat application, using the LiveTimer to constantly poll for new chat messages.
- "Stream" constantly updated data (such as sports scores, stocks, or weather conditions) to the browser.
- Create a web-based email system that checks for new mail and displays messages when it arrives.
- Make an online auction system that updates the current bids in real time.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for initializing and starting a LiveTimer
<cc1:LiveTimer id="LiveTimer" runat="server" Interval="100" Enabled="true">
</cc1:LiveTimer>
Code-Behind Example
The LiveTimer is also quite easy to configure/use in Code-Behind.
// Configure and start the timer
LiveTimer1.Interval = 100;
LiveTimer1.Start();
// Tick event raised every 100 milliseconds.
private void LiveTimer1_Tick(object sender, System.EventArgs e)
{
LiveLabel1.Text = DateTime.Now.ToLongTimeString();
LiveWrapper ASP.NET Server Control Information
This page includes information about the LiveWrapper Server Control, which is included in PowerWEB LiveControls for ASP.NET:
The LiveWrapper control contained with the LiveControls for ASP.NET suite provides callback interop support for complex 3rd party and Microsoft controls.
Browser Compatibility
LiveControls have been tested and are fully "callback-compatible" in the following browsers:
- Microsoft Internet Explorer 5.0+ for Windows
- Microsoft Interner Explorer 5.0+ for Macintosh
- Netscape 7.1+ for Windows
- Netscape 7.1+ for Macintosh OS X
- Mozilla 1.3+ for Windows
- Mozilla 1.3+ for Macintosh OS X
- Firefox for Windows
- Firefox for Macintosh OS X
- Camino for Macintosh OS X
- Konqueror based engines
- Galeon
- Opera 5.0+
If a browser which is not compatible accesses a page containing LiveControls, the controls will fall back to the standard ASP.NET functionality. For example, a LiveButton issues a transparent callback when clicked. If on a non-compatible page, the button will still be displayed, but will cause a standard postback when clicked.
Server Tag Example
The following tags demonstrate typical settings for a LiveWrapper control
<cc1:LiveWrapper id="LiveWrapper" runat="server">
Note about code-behind usage: Due to the complexities of rendering 3rd-party controls in a callback, it is not advised to dynamically create a LiveWrapper control for code-behind use.
Purchase Options
Customize your product and support options match your needs. Discounts are applied when products are purchased in multiples or within available product suites.
Have any questions about purchasing? See our Sales FAQ