UltraWebChart(TM)

.NET Chart Control
for ASP.NET

Version 3.00.20033.51.00 - October, 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 UltraWebChart. Be sure to read through the help file topics for important information on how to best use UltraWebChart.

.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 in v3.00.20033:
Axes
 - Logarithmic Axes
Layers
 - Layers infrastructure exposed to user
Stacked charts (New Charts)
 - Stacked Column 2/3 D
 - Stacked Bar 2/3 D
Multi chart (New Charts)
 - Line Bar
 - Scatter Line
 - Multi Pie 2/3 D
New chart types
 - Radar chart 2D
 - Spline Area 2D
 - Spline Line 2D
 - Doughnut 2/3 D
Data
 - Data Viewing (graphics in chart scroll bar)
 - Data Zooming (graphics in chart scroll bar)
 - Null Data support
 - Drill-down
Data Support
 - XML
 - Stream
 - Object collection
 Events
 - Data Item Over event
 - Data Item Out event
 - Data Drill down event
 - Data Error
Tool tips
 - Multi value tool tips
Web thin client (thick client look and feel)
 - Cross hair
 - Data highlighting for limited 2D charts
 - Tool-tip drill down
Color Models
 - Color Palettes
 - Color Gradients
Borders
 - Round border support
Persistence
 - Save and Load Chart style           
Adornments
 - Constant lines
 - Constant Areas
 - Coloring hints Call back
New Samples and improved documentation

  ClientSideEventsEditor:
Adding a handler for a ClientSideEvent is now just as easy as adding a server-side event handler.  Clicking on the ClientSideEvent name at design time will drop down a list of JavaScript functions currently defined on your WebForm.  There will also be an option to Add a New Function.  When this option is chosen, a new JavaScript function stub will automatically be generated for you and added to your WebForm.  You will automatically be brought to the new function, and you can start writing your code to handle the event.

  Design-Time HTML Intellisense:
To enable Design-Time HTML Intellisense, Right-Click on the control.  You will notice there is an option to "Enable HTML Intellisense".  Clicking on this option will put an extra attribute in the WebForm's body tag.  This attribute will allow Intellisense to work at design time, for the HTML view of the webform.  When you are done working with the HTML, you can turn off this option and remove the attribute by again Right-Clicking on the control, and unchecking the "Enable HTML Intellisense" option.

 

Upgrading to Version 3:
Version 3 of UltraWebChart appends a .v3 to the end of ALL the assembly names (this includes Infragistics.UltraChart.Render.ActiveImage.v3.dll) 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 3 you should make a backup copy of all files in the project.

To upgrade an existing project to version 3, follow these steps:

1. After opening the version 1 project, click on Project References and remove the entry for Infragistics.WebUI. UltraWebChart.dll.  Right-click to add a reference and select Infragistics.WebUI. UltraWebChart.v3.dll from the list of available .NET components.

2. If you attempt to open an aspx form containing UltraWebChart, 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. UltraWebChart to Infragistics.WebUI. to UltraWebChart.v3.  Perform the same change for Infragistics.UltraChart.Render.ActiveImage.v3.   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 WebChart v3 will be loaded in place of the v1 version.

3.  Open the ImagePipe.aspx page of your project.  Go to the HTML View for this page. .  In the <%@ Register TagPrefix directive at the top, change the Assembly attribute from Infragistics.WebUI. UltraWebChart to Infragistics.WebUI. to UltraWebChart.v3.     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 WebChart v3 ImagePipe will be loaded in place of the v1 version.

4. Open the file called licenses.licx in your project directory with notepad and change the reference from Infragistics.WebUI. UltraWebChart.dll to Infragistics.WebUI. UltraWebChart.v3.dll.  Save the licenses.licx file.

5. The names of the default virtual directories for images and script have been changed from \ig_Scripts and \ig_Images to ig_common\webchart3.    Be sure that the JavaScriptFileName property of the control has been updated to reflect that.

6. Delete the file Infragistics.WebUI. UltraWebChart.dll from the bin directory of the project so that only the Infragistics.WebUI. UltraWebChart.v3.dll file remains.  This will eliminate runtime errors due to multiple references to objects.

Script and Image Files:
This version of WebChart installs images and JavaScript files into a standard directory structure.  The location for scripts and images is determined by reading the registry entry:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\INetStp\PathWWWRoot.  If that is set to the IIS default then these files are installed to C:\inetpub\wwwroot\aspnet_client\infragistics\WebChart3.  If this registry entry is not found then the files are installed to c:\program files\common files\infragistics\web\WebChart3.  The virtual directories that map to these physical directories are named ig_common\webchart3.

UltraWebChart has a Client-Side Object Model (CSOM).  To support this functionality, a common javascript file is shared by all of the Infragistics WebControls.  The location of this file is specified using the JavaScriptFileNameCommon property.  By default, it is in a virtual directory /ig_common/scripts/ig_csom.js which maps to the physical path c:\inetpub\wwwroot\aspnet_client\Infragistics\Scripts\ig_csom.js.

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.dll assembly must be copied to the local project directory along with the UltraWebChart assembly in order to run the Web application under IIS.

Running Samples
According to the following Microsoft KB Articles
http://support.microsoft.com/default.aspx?scid=kb;en-us;316675&Product=NETFrame

http://support.microsoft.com/default.aspx?scid=kb;en-us;810204&Product=NETFrame

On Windows XP and Windows 2003 server 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.

This may result in one of the following:

Error:

The Microsoft Jet database engine cannot open the file 'C:\MyDB\Nwind.mdb'. It is already opened exclusively by another user, or you need permission to view its data.

-or-

Operation must use an updateable query.

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 .NET framework, 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 framework is installed. In order to open files for reading and writing, this account needs higher privileges.

To work around this problem, use one of the following methods:

1.  Configure the ASP.NET worker process (Aspnet_wp.exe) to run under the SYSTEM account in the <processModel> section of the Machine.config file.

2.  For security reasons, Microsoft recommends that you enable impersonation on your ASP.NET application. This method works if the impersonated user has necessary permissions to the computer and the database that you are accessing. You can enable impersonation either in the machine.config file of the development machine or the web.config file of the sample.  The machine.config file can be found at C:\WINNT\Microsoft.NET\Framework\v1.0.3705\CONFIG.

3.  Grant read and write permissions for the "Everyone" group on the database and the database folder. This method is not safe; therefore, Microsoft does not recommend this method.

Installation of Samples
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 UltraWebChart and then v3.00.

 

2) run CHARTremovevd.bat  This file takes 2 parameters, the first is the drive where UltraWebChart is installed.  The second is the full path to where UltraWebChart is installed.  Here is an example of what it would look like for a default install:


CHARTremovevd “c:” "c:\program files\infragistics\ultrawebchart\v3.00\”

This will remove the virtual directories that may be present from a previous install of UltraWebChart.

 

3) run CHARTmakevd.bat  This file takes 3 parameters, the first is the drive where UltraWebChart is installed.  The second is the full path to the samples directory.  The third is the full path to the ig_common directory.  Here is an example of what it would look like for a default install:

CHARTmakevd “c:” "c:\program files\infragistics\ultrawebchart\v3.00\samples" "C:\inetpub\wwwroot\aspnet_client\infragistics"

 

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_common, click next and browse to the ig_common directory.  By default it is C:\Inetpub\wwwroot\aspnet_client\Infragistics.

 

5) Click Next, then Finish.

 

6) Repeat steps 3-5 to create ig_ultrawebchart3samples (the default path is c:\program files\infragistics\ultrawebchart\v3.00\samples)

 

7) Under Default Website there should now be an entry for ig_ultrawebchart3samples.  Expand this. 

 

8) Expand UltraWebChart, then CS.  For each directory under here right click, and select properties.  Click on the Create button under Application settings.  Do the same for the directories under the VB 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_common/WebChart3 virtual directory within IIS in order to be accessed at runtime.  By default, the product installation maps this directory to C:\Inetpub\wwwroot\aspnet_client\Infragistics\WebChart3.  If you receive updates for JavaScript files, they should be placed into this directory to overwrite the older copies.

Known Issues:
- ToolTipsAndEvents Samples throw a System.Web.HttpRequestValidationException on ASP.NET 1.1.

The ToolTipsAndEvents samples only demonstrate the capability of developers to specify formats at design and/or run-time.  It is not recommended that production chart applications accept direct end user input for these properties’ values.

For backwards compatibility with ASP.NET 1.0, the directive necessary to prevent this exception from being thrown is not included in the Samples distribution.

The following directive can be placed at the top of Default.aspx in the CSToolTipsAndEvents and VBToolTipsAndEvents samples to disable request validation on this particular page,

RequestValidate="false"

such that the page directive reads on line 2 of CSToolTipsAndEvents/Default.aspx reads:

<%@ Page language="C#" Codebehind="Default.aspx.cs" AutoEventWireup="false"
 Inherits="CSToolTipsAndEvents.WebForm1" RequestValidate="false" %>

and that on line 2 of VBToolTipsAndEvents/Default.aspx reads:

<%@ Page language="VB" Codebehind="Default.aspx.vb" AutoEventWireup="false"
 Inherits="VBToolTipsAndEvents.WebForm1" RequestValidate="false" %>

 

Version Numbers:
After careful input from our development team and Enterprise customers we have modified our version number system for the Vol. 3 release.

Because of issues with version in .NET the system uses a couple of parts.  To avoid issues with side-by-side versioning the GAC file names contain the major version as part of the file name. 

Examples

Infragistics.Win.UltraWinGrid.v3.dll
Infragistics.WebUI.UltraWebNavigator.v3.dll

The .v# in the file name is used to indicate a major new version.

The current system of version number will be changed to allow customers to easily tell a large volume of information from the version number.  The first digit will contain the major version number of the control.  This is different from the volume number of the entire toolset because not every control is modified in every release.

The second digits are for minor revisions to the control and will be used to denote minor modification to a control that does not reach the level of a major release but are greater than a hotfix, such as an addition of a handful of properties, methods, or events.

The third set of digits is for the year and volume number that control was last released in.

The final set of digits is the build number.  This is increased each time a build is dropped to our internal QA area.  All of these builds are not sent out to customers.

The final set of digits also easily notifies you that this is a full regression tested build or a hotfix.  If the build number starts with 100X it is not regression tested and is a hotfix build.  If the build does not start with 100X it is a fully tested release.

Examples

3.00.20033.5 = Beta 1
3.00.20033.10 = 5 drops later Beta 2
3.00.20033.11 = 1 drop later Gold 2003 Volume 3 release
3.00.20033.1012 = 1 drop later First hot fix
3.00.20033.1017 = 5 drops later hot fix
3.00.20041.18 = 1 drop later Gold 2004 Volume 1 release
3.00.20041.1019 = 1 drop later First hot fix
3.00.20041.1024 = 5 drops later hot fix
4.00.20042.1 = Beta 1 with major new features

 

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=36&articlestypebugfix=on

UltraWebChart 3.00.20033.51.01– October, 2003
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Initial Release

UltraWebChart 1.00.6007.63.01– February, 2003
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Full Release containing all previous Hot Fixes

UltraWebChart 1.00.6007.57.01– December, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Full Release

UltraWebChart 1.00.6007.20.01– August, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Full Release

UltraWebChart 1.00.6007.17.00 – June, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Initial Release