AI at combit – a look behind the curtain

Since the release of ChatGPT, the world of artificial intelligence (AI) has changed rapidly. You’ve probably already had experience with tools like ChatGPT or GitHub Copilot that take developer workflows to a new level. At combit, we’re also open to the possibilities that AI offers, and are continuously integrating them into our own processes.

New Web Report Designer and Web Report Viewer Features in List & Label 29

List & Label’s most recent version 29 is coming along with quite a fe exciting news for the Web Report Designer and the Web Report Viewer. These updates provide improved functionalities and enhanced usability to developers and end users alike.

Web Report Viewer for Preview in Web Applications

web report viewer desktop

Up until version 27, you were able to use the HTML5 Viewer in your own .NET web applications in order to display a report preview directly in the browser. Interactive user actions such as drill down, filtering data using report parameters and much more were already possible. But the technology that was utilized for this is getting older now, as for example the jQuery framework. With the new Web Report Viewer, we have created a modern, highly compatible replacement, which has been available since version 27 (year 2021).

Revisiting C# Script Performance

This is another often overlooked feature – you can add scripts to your projects and use your favorite language to do so. Since a couple of versions already, List & Label supports C# Scripts. However, the performance was less than perfect, making it a good choice for complex calculations but not so much for using it on a line-to-line base. In List & Label 26, we were able to push the performance quite remarkably – now using scripts is perfectly feasible.

Making-of: Web Report Designer in Development Part I

The rapidly increasing number of web apps has led to a great demand for web-based reporting solutions. We followed this trend with List & Label, and moved the Designer to the web – from version 27 on. One huge benefit, brought by the new Designer: way less effort, because only one front- and back-end needs to be developed and subsequently maintained. Naturally, the development of the new Web Report Designer presented us with technical challenges which we’d like to share with you – maybe knowing about our own learning curve is going to help you with your own projects, too.

Porting to .NET Core: Report Server on New Technology Basis

report server ansichten endgeräte

The Report Server saw the light of day in 2014. At that time, version 1.0 was implemented using the ASP.NET MVC framework and was based on List & Label 19. But as the number of users increased in subsequent versions, so did the requirements and ideas for new features. Some of the customer requests were difficult to realize with the underlying technology. Many developers have certainly been faced with the same question: What should we do next?

 

Full Support for .NET Core 3.0

.net core 3.0

.NET Standard and .NET Core have been around for a while now. We jumped the bandwagon early and offered beta support since LL23 while officially supporting the new framework since List & Label 24. With the advent of .NET Core 3.0, Microsoft announced that the .NET 4.x releases will be the last of their kind and .NET Core 3.0 – which will later simply be called .NET and will be named ".NET 5" in its next release – is the place to go. We're already there.

Keeping Groups of Table Lines Together

Continuing our quest to make the table object more versatile and powerful in LL25, we added an important tweak to the way table lines are kept together. Before, you just had the choice between keeping all lines together or none. That means, if the output for a single record stretched over a couple of pages and consisted of several line definitions, there was hardly ever a way to get the wrapping "right".