UltraWebGrid(TM)
.NET
Grid Control
for ASP.NET
Version 2.1.20033.03.01 - 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 UltraWebGrid. Be sure to read through the help file topics for important information on how to best use UltraWebGrid.
.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 v2.1.20033:
- WebSchedule support
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 2:
Version 2 of UltraWebGrid 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.UltraWebGrid.dll. Right-click to add a reference and select Infragistics.WebUI.UltraWebGrid.v2.dll from the list of available .NET components.
2. If you attempt to open an aspx form containing UltraWebGrid, 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.UltraWebGrid to Infragistics.WebUI.UltraWebGrid.v2. 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.UltraWebGrid.dll to Infragistics.WebUI.UltraWebGrid.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 and \ig_Images to ig_common\webgrid2. Be sure that the JavaScriptFileName property of the control has been updated to reflect that.
5. Delete the file Infragistics.WebUI.UltraWebGrid.dll from the bin directory of the project so that only the Infragistics.WebUI.UltraWebGrid.v2.dll file remains. This will eliminate runtime errors due to multiple references to objects.
Script and Image Files:
This version of WebGrid 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\WebGrid2. If
this registry entry is not found then the files are installed to c:\program
files\common files\infragistics\web\WebGrid2. The virtual directories that map
to these physical directories are named ig_common\webgrid2.
UltraWebGrid 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 UltraWebGrid assembly in
order to run the Web application under IIS.
Browser
Support
The UltraWebGrid control
has two modes of browser support: Uplevel and Downlevel. When the
BrowserTarget property is set to Auto, UltraWebGrid considers Internet Explorer
5.5 and above and Netscape 6.0 and above to be up-level browsers and all other
browsers including Netscape 4.x are considered down-level browsers. 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 5.5 and above,
UltraWebGrid is optimized for that environment.
Creating
Applications
When UltraWebGrid is added
to an application by placing it within a web page, two assemblies are added to
the project references list: Infragistics.WebUI.UltraWebGrid.dll and
Infragistics.WebUI.Shared.dll. Infragistics.WebUI.Shared.dll is installed into
the Global Assembly Cache (GAC) and therefore, its CopyLocal property needs to
be set to true. This enables ASP.NET to locate the assembly at runtime since,
by default; the GAC is not searched at runtime.
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 UltraWebGrid and
then v2.1.
2) run GRDremovevd.bat This file takes 2 parameters, the first is the drive
where UltraWebGrid is installed. The second is the full path to where
UltraWebGrid is installed. Here is an example of what it would look like for a
default install:
GRDremovevd“c:” "c:\program files\infragistics\UltraWebGrid \v2.1\”
This will remove the virtual directories that may be present from a previous
install of UltraWebGrid.
3) run GRDremovevd.bat This file takes 3 parameters, the first is the drive
where UltraWebGrid 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:
GRDmakevd “c:” "c:\program files\infragistics\ultrawebgrid\v2.1\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_ultrawebgrid2samples(the default path is
c:\program files\infragistics\ultrawebgrid\v2.1\samples)
7) Under Default Website there should now be an entry for
ig_ultrawebgrid2samples. Expand this.
8) Expand UltraWebGrid the CS. For each directory under CS right click, and
select properties. Click on the Create button under Application settings. Do
the same for each directory 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/WebGrid2
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\WebGrid2. If you receive
updates for JavaScript files, they should be placed into this directory to
overwrite the older copies.
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=92&articlestypebugfix=on>
UltraWebGrid 2.1.20033.03.00 – October, 2003
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Initial Release
UltraWebGrid 2.00.5000.17.01 – June, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Full Release containing all previous Hot Fixes
UltraWebGrid (2.00.5000.17)
WebCombo (2.00.5000.17)
UltraWebGrid 2.00.5000.01.00 – March, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Initial Release
UltraWebGrid
1.00.6007.49.01 – January, 2003
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Full Release containing all previous Hot Fixes
UltraWebGrid (1.00.6007.49)
UltraWebGrid
1.00.6007.48.01 – December, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Full Release
UltraWebGrid
1.00.6007.32.01 – August, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Full Release
UltraWebGrid
1.00.6007.22.00 – May, 2002
-------------------------------------------------------------------------------------------------------------------------------------------------------------
- Initial Release