Supporting SVG as Image Format

The Scalable Vector Graphics format has been around for quite a while. The first specification was released in 2001, and meanwhile all browsers offer solid support for SVG. During the years, we've received a couple of requests to support SVG in List & Label. Initially, I was hoping for Microsoft to make SVG rendering support a Windows feature that we could just use. However, that hasn't happened so far. And so we had to come up with a different solution.

Signal Ranges Extended to Charts

The signal ranges are a handy gauge feature to highlight parts of the scale. It enables you to divide the scale e.g. into a green, yellow and red part. That way, you can judge at a glance if a value is "good" or "bad". In LL23, this feature has been extended to charts.

Supporting Cross-Datasource Relations

The .NET DataProvider concept allows to bind to almost any data source. Basically, it mimics a relational database management system containing tables, relations, sort orders etc. However, often you'll find yourself needing to combine data from different sources, e.g. a server log file that contains customer logins and a SQL customer database that contains all pertinent information about the customers.

New Features in the Report Server – Part 2

select chart type

As promised, today I’d like to report on even more of the updates in Report Server 23. The updates are particularly impressive in the ad-hoc Designer, which provides support for fast creation of simple tables and diagrams. As opposed to the extensive Report Server Designer, only the most important setting options are provided here. In addition, the ad-hoc Designer is likewise available as a separate component in List & Label 23.

Using Your Own .NET Designer Objects in Unmanaged Code – Designer Object Bridge

Many things can often be implemented significantly easier and faster in managed code than in unmanaged code, such as with Delphi or C++. Sometimes, there already exist ready-made .NET modules which contain the desired requirements and which need to be used in your own unmanaged application. But the question then is: How can a .NET module be made accessible to an unmanaged system?