Dundas Chart for .NET - OLAP Services v5.5 Now in Beta!
This month marks the release of the Beta version of Dundas Chart for .NET - OLAP Services
version 5.5. One of the main features of this new release is the
introduction of the grid control. This means end users can
complement their charts with a numerical analysis that allows for a
more complete overview of multidimensional data. Another feature of
this new release is that we have changed the core Chart within our OLAP product from version 5.0 to 5.5.
Because of this, all of the new Chart v5.5 functionality, such as
breaks, 2D drawing effects, and much more will now be available in
our OLAP product. The Beta program provides a download of our
product which is free and unrestricted.
read more »
Client Side Functionality Available for Reporting
During run-time all Dundas products for Reporting Services are
rendered as report item images. Thus, all Reporting Services
controls are limited by the
interactivity provided by Microsoft for the Reporting Services Image
Control. That said, there is some client side functionality
available for controls for Reporting Services:
Adding client side functionality can greatly increase the ease of
usability of your reports
for the user.
- Tooltip for the entire control
- Drill-down to another report or website in a new or existing browser window using hyperlinks
- Ability to change the data the report is using through report parameters. This functionality allows the user to specify filters during run-time
Dundas Controls in Reporting Services 2000
All Dundas Reporting Services products are designed for
Microsoft Reporting Services 2005. However, it is possible to
use Dundas ASP.NET controls in reports for Microsoft Reporting
Services 2000. Any Dundas control that supports
BinaryStreaming can be used in this manner. While the
specific steps are outlined in the full article, the summary of the
process is as follows:
read more »
- Setup an ASP.NET environment and drop a Dundas control onto a web-form.
- Delete all HTML tags on the ASP.NET page aside from the Dundas control
Set the RenderType of the Dundas control to BinaryStreaming.
- Add this.Page.Response.Charset = ""; to the Page_Load event.
- Create a new report for Reporting Services 2000 and add an Image control to the report.
- Point the Image control to the created webpage that contains the Dundas control.
Image Animation Demo
The growing animation demo shows how Chart can be manipulated
particular effect can be very
useful in dashboards or other data aggregation views where you may want to hide the
bulk of the Chart data until the user wishes to see it. This has the
benefit of saving
screen space for other things until a detailed look at the Chart is
Image Animation Demo
This demo also uses the Chart control for both the small icon and the large picture. While this is
convenient to show that Dundas Chart is robust, a static image
can also be used for the icon to save resources and bandwidth.
The full article contains the source code for this sample.
read more »
How to use Dundas Chart for ASP.NET in IIS6 Isolation Mode
With IIS6, many new and exciting features are available to serve website content
that were not available previously. One such feature is WebGarden Application
Dundas Chart v5.5 can be used in a WebGarden environment with no
modifications if none of the rich client-side features have been enabled, such as
zooming and scrolling and the toolbar. However, if these features are used, a
few changes are required in order for Chart to work properly and are necessary
due to the way WebGarden memory is shared across processes by IIS. Please refer to the
full article for a step-by-step explanation of what is required when using
Dundas Chart v5.5 in a WebGarden environment with rich client-side features.
read more »
Performance and Optimization
Dundas Gauge for .NET has several different factors affecting its
performance. These optimization techniques can greatly increase
performance while still being easy to change. Before listing the
optimization techniques, it is important to identify the main issues
that affect performance on each platform:
There are two main areas of concern for performance and optimization, they include:
- The amount of time it takes the gauge control to render the
image. This is largely related to the complexity, and size of the Gauge
- The amount of time it takes to stream the gauge image from
the server to the client, which is directly proportional to the size of
the gauge image generated.
The refresh rate, which is set using the RefreshRate
property, determines how often the control is refreshed. The refresh
rate is measured in redraws per second, and the lower the refresh rate,
the greater the overall performance of the gauge.
Decreasing the refresh rate may cause the motion of pointers in the
gauge to become "choppy" or erratic. Since the refresh rate impacts
performance more significantly than any other single factor, it is
important to strike a fine balance between an optimal refresh rate, and
Since the main issues affecting performance have been identified, the properties that can increase performance
can now be considered. Below is the major factors
and their associated properties so that you can quickly make changes to Gauge within
your own project.
- (ASP.NET only) Image Size and Type - Controlled through the RenderType property as well as the Width and Height properties
- AntiAliasing - Two properties are available for AntiAliasing: AntiAliasing and TextAntiAliasingQuality.
- Frames - The BackFrame object within Gauge controls this.
- Calculated Values - Contained within the Values collection.
- Gradient Colors - These colors are controlled by a variety of properties in each class which they can appear in.
- Semi Transparency - When using the Color.FromArgb() function, the alpha value controls transparency.
For more information, including information on why these specific
properties are important to performance, please refer to the article Performance and Optimization within the help documentation.
How to Reduce Map Storage Space Through Simplification
In the Dundas Map control, imported shapes can be highly detailed and it
can take megabytes of space to store information about all of the
points and segments that make up the shapes. Sometimes, this is so much
information that the control reacts slowly. If your Map control's
maximum zooming range (set in MapControl.Viewport.MaximumZoom) does not
need this level of detail to display your shapes, consider using
simplification to remove some of it.
Dundas Map includes a
Simplify() method to perform simplification
automatically. Simply call this method and supply a float value argument as your desired simplification factor.
The argument should be greater than zero, but the value that you choose
depends on how closely you can zoom into your map, and how much detail
you feel is needed.
read more »