Using Access Data on an ASP.NET Web Page
You can now use the database in a Web page. This part of the walkthrough uses an AccessDataSource control and a DataList control.
To add AccessDataSource and DataList controls to the page
- Open the Default.aspx page (or another page that you want to use) and switch to Design view.
- From the Data group in the toolbox, drag an AccessDataSource control onto the page.
Note If the Access Data Source Tasks menu does not appear, right-click the control and then click Show Smart Tag.
- On the Access Data Source Tasks shortcut menu, click Configure Data Source. The Configure Data Source wizard is displayed.
- On the Choose a database page, in the Microsoft Access Data file box, type ~/App_Data/Northwind.mdb or use the Browse button to select the .mdb file.
- Click Next to open the Configure Select Statement page, and then click Specify columns from a table or view.
- In the Name list, click Categories.
- Select the CategoryName and Description check boxes and then click Next.
- Optionally, click Test Query to test your query.
- Click Finish.
- From the Data group in the toolbox, drag a DataList control onto the page.
- On the DataList Tasks menu, in the Choose Data Source box, click AccessDataSource1.
- Click Ctrl+F5 to run the page with the default layout.
- Close the browser.
Microsoft Web Application Stress Tool 1.1
------------------------
Installation Notes
------------------------
Microsoft Web Application Stress Tool requires Microsoft
Windows NT version 4.0 Service Pack 4 or above and Microsoft
Internet Explorer version 4.0 or above.
------------------------
Online Support
------------------------
To check for the latest news and updates regarding this tool
you can go to the web site http://webtool.rte.microsoft.com.
This web site contains a knowledge base that provides
in-depth answers to performance testing questions and
additional information on the most frequently asked
questions.
------------------------
Known Issues
------------------------
Web Application Stress Tool only supports stress against one
server or DNS name at a time.
To use authentication, you must add users with valid user
names and passwords.
To record, you will need to modify your browser settings if
using a browser other than, or prior to, IE 5.0. See online
help for more information.
Webtool respects the "user-agent: stress-agent" directive in
the ROBOTS.TXT file on a web server and will not start a
stress test against a server or domain that contains this
file with this directive. This file should be located in
the root directory of your web site
In general, you should NOT install the WebTool service on
the web server you are testing since this may interfere with
your results.
The Web Application Stress Tool object model can be used to
start, stop, and configure a test run. However, this feature
cannot be used to modify a running test in this version of
the tool.
Web Application Stress Tool is year 2000 compliant.
IMPORTANT: Start your test with a small number of
Concurrent Connections and then work your way up to the
desired stress level slowly, watching the processor
utilization on the clients and web server. If the
processor utilization is consistently above 90% on one or
more machines, the test is probably invalid. If this
occurs, decrease the number of concurrent connections or
add more client machines to handle the desired stress load.
On-line help contains a discussion of performance testing
techniques.
Although there is no hard limit on the number of script
items you can have in one script, the most practical limit
is 3000 script items. Beyond that you will find that it
takes an inordinately long time to start and stop tests.
What's New in Internet Explorer 8
64-Bit Downloads
Internet Explorer now supports download of files whose size exceeds 4 gigabytes (GB). Users of Internet Explorer 8 can take advantage of this functionality by default. Third-party extensions need to implement IBindStatusCallbackEx and return BINDF2_READ_DATA_GREATER_THAN_4GB from their GetBindInfoEx callback method. Download progress is reported through OnProgress by using the BINDSTATUS_64BIT_PROGRESS flag. These callback methods are supported by IMoniker::BindToObject and IMoniker::BindToStorage.
Accelerators
Because the Internet has become increasingly interactive, Internet Explorer 8 makes it easier to interact with content on a Web page. Accelerators are a type of browser extensions that act on Web page content by sending the information to a service of the user's choosing. Services then perform actions on the content (such as "email" or "bookmark") or provide more information ("translate" or "map"). Users can install and access Accelerators from the browser shortcut menu, making their browsing experience more efficient.
For more information, see OpenService Accelerators Developer Guide.
Accessibility and ARIA
In response to the increase in user interface (UI) complexity on the Web, the Web Accessibility Initiative World Wide Web link group has defined a roadmap for Accessible Rich Internet Applications (ARIA), which introduces ways for Web site authors to define how custom UI elements are accessed. ARIA accomplishes this by defining a set of HTML attributes that map back to common UI controls. As a result, users with disabilities can access Web sites with a rich interaction model. By exposing ARIA through the Microsoft Active Accessibility API in Internet Explorer 8, assistive technologies that already use Microsoft Active Accessibility can also support ARIA easily.
* The alt attribute is no longer displayed as the image tooltip when the browser is running in IE8 mode. Instead, the target of the longDesc attribute is used as the tooltip if present; otherwise, the title is displayed. The alt attribute is still used as the Microsoft Active Accessibility name, and the title attribute is used as the fallback name only if alt is not present.
* ARIA attribute syntax is the same in both IE8 mode and IE7 mode. Earlier releases of Internet Explorer 8 required a legacy property syntax when setting ARIA attributes in compatibility view. For cross-browser compatibility, always use the WAI-ARIA attribute syntax to access and modify ARIA properties, for example object.setAttribute("aria-valuenow", newValue).
For more information, see:
* ARIA Implementation Guide for AT Vendors: Internet Explorer 8
* Mapping ARIA Roles, States, and Properties to UI Automation
* What's New for Accessibility in Internet Explorer 8
ActiveX Improvements
Internet Explorer 8 offers greater control over your Microsoft ActiveX installation and debugging.
* Per-site ActiveX Nearly half of all ActiveX controls meant to run on only one site do not use any form of site locking technology. This means that many controls are not secure by default and could be misused by malicious Web sites. To prevent this in Internet Explorer 8, users can decide whether to allow ActiveX controls to run on a site-by-site basis. For more information, see Per-Site ActiveX Controls.
* Non-administrator installation Standard users (those without administrator privileges) can install ActiveX controls to their user profiles without a UAC prompt or administrator involvement of any kind. In the event that a user does install a malicious ActiveX control, only the user profile is affected; the system itself is not compromised. For more information, see Non-Admin ActiveX Controls.
* ActiveX Logging Internet Explorer 8 can report the most common installation and instantiation failures, such as security restrictions preventing an ActiveX control from being instantiated properly. ActiveX logging is performed the same as other Internet Explorer compatibility logging, by using the Internet Explorer Application Compatibility Toolkit. For more information, see Using the Internet Explorer Compatibility Test Tool.
AJAX Enhancements
Asynchronous JavaScript and XML (AJAX) is changing the way Web applications are built. Internet Explorer 8 brings new functionality to the XMLHttpRequest object that enables AJAX applications.
* AJAX Navigation Client requests that do not trigger traditional Web page navigation can now update the hash property, which allows the Back button to function appropriately.
* Connection Events Where data reliability is a priority, AJAX applications can choose to save data locally if they are disconnected from a network. See onoffline, ononline.
* Connections Per Server Internet Explorer 8 raises the number of connections per host by default, for a potential drop in Web page load times and increased parallelism in AJAX scenarios.
* Cross-document Messaging Documents in different domains can securely exchange data using postMessage. Documents that receive messages listen for the onmessage event.
* Cross-domain Request (XDR) To allow developers to more safely combine services from different Web sites, the XDomainRequest object restricts and secures communication between untrusted modules in a Web page. The browser shields the user from potential threats while allowing powerful cross-site interaction.
* Timeout Requests Internet Explorer 8 adds the ability to set a timeout property on server requests.
* Sanitize HTML Easily remove event properties and script from HTML fragments with window.toStaticHTML.
* Native JSON Support JavaScript Object Notation (JSON) objects (used widely in AJAX scenarios) can now be serialized and parsed directly in Microsoft JScript. Use JSON.stringify to transform object data to a string and JSON.parse to revive JSON-formatted text. You can also fine-tune your object's output by implementing a toJSON method. These new methods are much faster than script, and safer than using eval.