UltraWebNavigator(TM)
.NET
Tree and Menu Control and Design Environment
for ASP.NET
Version 2.00.5000.112.01 - June, 2003
(C) Copyright Infragistics, Inc., 2001-2003
Infragistics, Inc. Windsor Corporate Park, 50 Millstone Road, Building 200 - Suite 150, East Windsor, NJ 08520
Voice 609-448-2000, Fax 609-448-2017, Internet http://www.infragistics.com
This document contains release notes for UltraWebNavigator Version 2. Be sure to read through the help file topics for important information on how to best use UltraWebNavigator.
.NET
Framework Compatibility:
All included
assemblies have been built against the Microsoft .NET framework 1.0 RTM build.
You must have either the 1.0 or 1.1 RTM build of the framework installed for
the product to work.
New Features of UltraWebTree
1. Support for Checkboxes on Nodes: Checkboxes can be displayed next to individual nodes, on all nodes at a particular hierarchical level, or on the tree as a whole. Node check events can be caught on the client or on the server and nodes can be checked on and off programmatically on the client or the server.
2. Support for Disabled Nodes: Individual nodes can be flagged as disabled so that they cannot be edited, selected or clicked on. The style of disabled nodes is completely configurable.
3. Support for Hidden Nodes: Individual nodes can be flagged as hidden so that they will not be rendered to the client.
4. Load on Demand capability: To reduce traffic over the wire and to increase viewstate efficiency, nodes can be populated with children on an as-needed basis. Two styles of load on demand functionality are supported: Manual and Automatic. With manual load on demand, the application is responsible for responding to the DemandLoad event and populating the children of the expanded node. Automatic load on demand can be used when binding to a database. In this case, UltraWebTree will populate only those nodes that are expanded at the time that the databind takes place. Using either of these techniques eliminates the need for non-expanded node children to travel down to the browser.
5. Single branch expand capability: With this property turned on, only the nodes of a single branch chain are displayed at one time. As a node in another branch chain is clicked, the currently open chain is collapsed. This feature helps to save on page real-estate and can also reduce transmission times if used in conjunction with the Load on Demand feature.
6. Selected Node image properties: Allows a different node image to be displayed when the node becomes selected.
7. Client side object model, API and events: A complete set of client-side capabilities that allows developers to respond to events in JavaScript, modify the tree in numerous ways, and fire events to the server when necessary. This exclusive technology enables more processing on the client and results in fewer server postbacks and a richer user experience.
8. Enhanced design time support: All new features are also available in the Infragistics UltraNavStudio design environment which allows trees to be designed interactively without the need for programming or XML knowledge. Designs can be saved to project files or output to HTML for immediate use. The design-time experience has also been enhanced in Visual Studio to allow for quick selection of preset styles or UltraNavStudio project files.
New Features of UltraWebMenu
1. Support for Checkboxes on menu items: Checkboxes can be displayed next to menu items using a configurable image file. Item check events can be caught on the client or on the server and items can be checked on and off programmatically on the client or the server.
2. Support for disabled menu items: Individual nodes can be flagged as disabled so that they cannot be edited, selected or clicked on. The style of disabled nodes is completely configurable.
3. Support for Hidden Menu Items: Individual items can be flagged as hidden so that they will not be rendered to the client.
4. Support for menu separators: Menu items can be marked as separators so that they appear as horizontal lines between other menu items. The style and look of the separator class is completely customizable.
5. Client side object model, API and events: A complete set of client-side capabilities that allows developers to respond to events in JavaScript, modify the menu in numerous ways, and fire events to the server when necessary. This exclusive technology enables more processing on the client and results in fewer server post-backs and a richer user experience.
6. Support for menu expansion effects using IE transitions: Menus can be enhanced in IE5+ with fade-in effects along with shadows of various kinds. Numerous parameters can be set to control the type, duration and style of the effects.
7. Support for Windows XP look and feel: Menus can be created that look and behave very similarly to Windows XP menus. Style presets as well as UltraNavStudio templates are available with a selection of XP menu styles.
8. Enhanced design time: All new features are also available in the Infragistics UltraNavStudio design environment which allows menus to be designed interactively without the need for programming or XML knowledge. Designs can be saved to project files or output to HTML for immediate use. The design-time experience has also been enhanced in Visual Studio to allow for quick selection of preset styles or UltraNavStudio project files.
9. Enhanced client-side menu behavior: Developers can choose from three styles of client-side menu behavior: Standard Web menu, Windows Client menu or XP Windows Client menu. These three styles provide different nuances of look and feel depending on the type of behavior desired.
10. Menu Hover images: As the mouse moves over menu items, the image can be switched to show an enhanced form of the image as in Windows XP.
Version 2 of UltraWebNavigator appends a .v2 to the end of the assembly name to help insure proper versioning in Visual Studio and to enable clean side-by-side execution with version 1 of the product.
Before upgrading your project to version 2 you should make a backup copy of all files in the project.
To upgrade an existing project to version 2, follow these steps:
1. After opening the version 1 project, click on Project References and remove the entry for Infragistics.WebUI.UltraWebNavigator.dll. Right-click to add a reference and select Infragistics.WebUI.UltraWebNavigator.v2.dll from the list of available .NET components.
2. If you attempt to open an aspx form containing UltraWebTree or UltraWebMenu, you will see the controls displayed as an error. To fix this, click the HTML tab at the bottom of the form and edit the aspx. file as text. In the <%@ Register TagPrefix directive at the top, change the Assembly attribute from Infragistics.WebUI.UltraWebNavigator.dll to Infragistics.WebUI.UltraWebNavigator.v2.dll. Upon completing this change you should immediately save the aspx file and close it. Do not switch back to design mode and make any changes to the file. Once the file has been saved and closed it can be reopened and the WebGrid v2 will be loaded in place of the v1 version.
3. Open the file called licenses.licx in your project directory with notepad and change the reference from Infragistics.WebUI.UltraWebNavigator.dll to Infragistics.WebUI.UltraWebNavigator.v2.dll. Save the licenses.licx file.
4. The names of the default virtual directories for images and script have been changed from \ig_Scripts to \ig_Scripts2 and from \ig_Images to \ig_Images2. Also, the names of JavaScript files and directories need to be changed. Change the JavaScriptFileName property from ig_WebMenu.js to ig_WebMenu2.js and ig_webTree.js to ig_webTree2.js.
5. Delete the file Infragistics.WebUI.UltraWebNavigator.dll from the bin directory of the project so that only the Infragistics.WebUI.UltraWebNavigator.v2.dll file remains. This will eliminate runtime errors due to multiple references to objects.
Running WebForms
Applications
In order to run
applications that use the Infragistics Web Controls on your machine,
you will need to set the Copy Local flag to True for the
Infragistics.WebUI.Shared.dll Assembly. This is because Web Applications,
by default, do not look in the GAC to resolve assembly references at
runtime. Therefore, the Infragistics.WebUI.Shared assembly must be copied
to the local project directory along with the UltraWebNavigator assembly in
order to run the Web application under IIS.
Browser Support
The UltraWebTree and UltraWebMenu
controls each have two modes of browser support: Up-level and Down-level.
When the BrowserTarget property is set to Auto, these components consider
Internet Explorer 5 and above to be up-level browsers and all other browsers
including Netscape 4.x and Netscape 6.x are considered down-level for the
purposes of DHTML execution compatibility.
UltraNavStudio only supports rendering to HTML files of up-level HTML code. If down-level rendering is required, then the igproj file can be loaded into the UltraWebMenu or UltraWebTree control at run-time and rendered appropriately for the user agent in use.
In general, the more cross browser support needed, the simpler the design of the control needs to be. This is due to the variety of browsers available and their different capabilities and means of rendering. Since the vast majority of browser use is with Internet Explorer, UltraWebNavigator is optimized for that environment.
Installation of Samples
On Windows XP machines,
the data binding samples may display an exception stating that the user does
not have access rights to the file or that the file is in use by someone else.
The cause of the problem is due to certain changes Microsoft made in the security settings and defaults for running Web applications on a Server. With the release version of Visual Studio.NET, Web applications running on the server are run under the ASPNET Windows account on the machine. This account is only given User privileges when .NET is installed. In order to open files for reading and writing, this account needs higher privileges. In order to change the privileges of this account, one must be logged onto the machine with Administrative privileges. When logged on with Administrative privileges, one can go into Control Panel - Users and Passwords and change the member groups of the ASPNET account on the local server machine. The privileges should be increased to Administrators group. At this point, the sample application will be able to access the database file at runtime.
The installation for the Infragistics Web Controls attempts to automatically install all samples into the IIS virtual directory structures on the target machine so that the samples can be run easily and the sample projects can be opened in Visual Studio .NET. However, under some circumstances, it may not be possible to complete this aspect successfully. Therefore, the following information can be used to manually install the samples and get them running in the event that the automatic installation fails.
There are two different methods you can use that you can resolve this problem.
Method 1 - Running the Batch File
1) open a command window. Navigate to the installation folder. By default this would be c:\program files\infragistics. From here, go to UltraWebNavigator and then v2.00.5000.
2) run navremovevd.bat This file takes 2 parameters, the first is the drive where UltraWebNavigator is installed. The second is the full path to where UltraWebNavigator is installed. Here is an example of what it would look like for a default install:
navremovevd c: "c:\program files\infragistics\ultrawebnavigator\v2.00.5000\
This will remove the virtual directories that may be present from a previous install of UltraWebNavigator.
3) run navmakevd.bat This file takes 4 parameters, the first is the drive where UltraWebNavigator is installed. The second is the full path to the samples directory. The third is the full path to the ig_images directory, and the fourth is the full path to the ig_scripts directory. Here is an example of what it would look like for a default install:
xpmakevd c: "c:\program files\infragistics\ultrawebnavigator\v2.00.5000\samples" "c:\program files\common files\infragistics\web\v2.00.5000\ig_images" "c:\program files\common files\infragistics\web\v2.00.5000\ig_scripts"
Note: Quotes must be included. The drive letters and directory names will be different if you did not use the default install path.
Method 2 - Manually configuring IIS
1) Open IIS Admin ( control panel->administrative tools->Internet Services Manager)
2) Expand Default Website
3) Right click Default Website and in the popup menu, select new->Virtual Directory
4) For Alias type ig_scripts2, click next and browse to the ig_scripts directory. By default it is c:\program files\common files\infragistics\web\v2.00.5000\ig_scripts.
5) Click Next, then Finish.
6) Repeat steps 3-5 for the ig_images2 directory (the default path is c:\program files\common files\infragistics\web\v2.00.5000\ig_images)
7) Repeat steps 3-5 to create ig_ultrawebnavigator2samples (the default path is c:\program files\infragistics\ultrawebnavigator\v2.00.5000\samples)
8) Under Default Website there should now be an entry for ig_ultrawebnavigator2samples. Expand this.
9) Expand UltraWebTree, then Cs. For each directory under here right click, and select properties. Click on the Create button under Application settings. Do the same for each directory under the VB folder.
10) Repeat step 9 for the UltraWebMenu folder.
All samples should now be ready to run.
Installation
of JavaScript Files
Correct installation of
the JavaScript file requires that it be copied to the ig_scripts2 virtual
directory within IIS in order to be accessed at runtime. By default, the
product installation maps this directory to c:\program files\common
files\Infragistics\Web\v2.0.5000\ig_Scripts. If you receive updates for
the JavaScript file, it should be placed into this directory to overwrite the
older copy.
Issues Addressed:
Use the knowledge base in the
Infragistics Support Center
http://www.infragistics.com/support/supportcenter.asp
to review the history of addressed issues.
http://www.infragistics.com/process/p_knowledge.asp?product=91&articlestypebugfix=on
UltraWebNavigator
2.00.5000.112.01 June, 2003
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Full Release containing all previous Hot Fixes
UltraWebNavigator.v2.dll (2.00.5000.112)
UltraWebNavigator
2.00.5000.107.01 March, 2003
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Full Release containing all previous Hot Fixes
UltraWebNavigator.v2.dll (2.00.5000.107)
UltraWebNavigator
2.00.5000.104.01 January, 2003
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Full Release containing all previous Hot Fixes
UltraWebNavigator
2.00.5000.102.00 December, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Initial Release