WPF Reporting
-
I need a reporting tool for use in a WPF app. Requirements: 1. Preferably free 2. The report will probably NOT be too complex, so I don't need anything too complicated. 3. Easy to learn 4. Easy to deploy. Any suggestions? Thanks!
If it's not broken, fix it until it is
-
I need a reporting tool for use in a WPF app. Requirements: 1. Preferably free 2. The report will probably NOT be too complex, so I don't need anything too complicated. 3. Easy to learn 4. Easy to deploy. Any suggestions? Thanks!
If it's not broken, fix it until it is
-
I need a reporting tool for use in a WPF app. Requirements: 1. Preferably free 2. The report will probably NOT be too complex, so I don't need anything too complicated. 3. Easy to learn 4. Easy to deploy. Any suggestions? Thanks!
If it's not broken, fix it until it is
-
You pointed me to Telerik. I downloaded their Reporting Q2 2014 samples. I can't get it to compile. There are 4 or 5 themes files that have to be included, or the viewer doesn't show up. Their tech support sent me this[^]. I followed it, and they theme files won't compile. Seems they are referencing other Telerik assemblies or namespaces that either don't exist or are wrong. What version of their reporting are you using? Have you got this working?
If it's not broken, fix it until it is
-
Pete, I downloaded it.. I don't see a designer anywhere... Am I missing something? Thanks
If it's not broken, fix it until it is
-
I need a reporting tool for use in a WPF app. Requirements: 1. Preferably free 2. The report will probably NOT be too complex, so I don't need anything too complicated. 3. Easy to learn 4. Easy to deploy. Any suggestions? Thanks!
If it's not broken, fix it until it is
If the report is simple and you have already worked getting the data to a form, maybe just roll your own print routine to generate the report? See Printing in WPF[^] for example?
-
Pete, I downloaded it.. I don't see a designer anywhere... Am I missing something? Thanks
If it's not broken, fix it until it is
It uses XAML so it doesn't have a designer. That wasn't a requirement in your list. To be honest, the XAML is nice and clean. This is the sample Image report:
<FlowDocument xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:xrd="clr-namespace:CodeReason.Reports.Document;assembly=CodeReason.Reports"
xmlns:xrbc="clr-namespace:CodeReason.Reports.Document.Barcode;assembly=CodeReason.Reports"
PageHeight="29.7cm" PageWidth="21cm" ColumnWidth="21cm">
xrd:ReportProperties
xrd:ReportProperties.ReportNameImageReport</xrd:ReportProperties.ReportName>
xrd:ReportProperties.ReportTitleImage Report</xrd:ReportProperties.ReportTitle>
</xrd:ReportProperties>
<xrd:SectionReportHeader PageHeaderHeight="2" Padding="10,10,10,0" FontSize="12">
<Table CellSpacing="0">
<Table.Columns>
<TableColumn Width="*" />
<TableColumn Width="*" />
</Table.Columns>
<TableRowGroup>
<TableRow>
<TableCell>
<Paragraph>
<xrd:InlineContextValue PropertyName="ReportTitle" />
</Paragraph>
</TableCell>
<TableCell>
<Paragraph TextAlignment="Right">
<xrd:InlineDocumentValue PropertyName="PrintDate" Format="dd.MM.yyyy HH:mm:ss" />
</Paragraph>
</TableCell>
</TableRow>
</TableRowGroup>
</Table>
</xrd:SectionReportHeader>
<xrd:SectionReportFooter PageFooterHeight="2" Padding="10,0,10,10" FontSize="12">
<Table CellSpacing="0">
<Table.Columns>
<TableColumn Width="*" />
<TableColumn Width="*" />
</Table.Columns>
<TableRowGroup>
<TableRow>
<TableCell>
<Paragraph>
</Paragraph>
</TableCell>
<TableCell>
<Paragraph TextAl -
It uses XAML so it doesn't have a designer. That wasn't a requirement in your list. To be honest, the XAML is nice and clean. This is the sample Image report:
<FlowDocument xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:xrd="clr-namespace:CodeReason.Reports.Document;assembly=CodeReason.Reports"
xmlns:xrbc="clr-namespace:CodeReason.Reports.Document.Barcode;assembly=CodeReason.Reports"
PageHeight="29.7cm" PageWidth="21cm" ColumnWidth="21cm">
xrd:ReportProperties
xrd:ReportProperties.ReportNameImageReport</xrd:ReportProperties.ReportName>
xrd:ReportProperties.ReportTitleImage Report</xrd:ReportProperties.ReportTitle>
</xrd:ReportProperties>
<xrd:SectionReportHeader PageHeaderHeight="2" Padding="10,10,10,0" FontSize="12">
<Table CellSpacing="0">
<Table.Columns>
<TableColumn Width="*" />
<TableColumn Width="*" />
</Table.Columns>
<TableRowGroup>
<TableRow>
<TableCell>
<Paragraph>
<xrd:InlineContextValue PropertyName="ReportTitle" />
</Paragraph>
</TableCell>
<TableCell>
<Paragraph TextAlignment="Right">
<xrd:InlineDocumentValue PropertyName="PrintDate" Format="dd.MM.yyyy HH:mm:ss" />
</Paragraph>
</TableCell>
</TableRow>
</TableRowGroup>
</Table>
</xrd:SectionReportHeader>
<xrd:SectionReportFooter PageFooterHeight="2" Padding="10,0,10,10" FontSize="12">
<Table CellSpacing="0">
<Table.Columns>
<TableColumn Width="*" />
<TableColumn Width="*" />
</Table.Columns>
<TableRowGroup>
<TableRow>
<TableCell>
<Paragraph>
</Paragraph>
</TableCell>
<TableCell>
<Paragraph TextAlPete O'Hanlon wrote:
It uses XAML so it doesn't have a designer. That wasn't a requirement in your list. To be honest, the XAML is nice and clean. This is the sample Image report:
To me it's assumed that you need a designer. Yes, XAML is nice & clean... and VERY time consuming. For anything other than a VERY simple report it would take all day to get laid out right. I noticed on their site that someone asked for a designer. Nice idea for an add on to the project. I can't see how any serious reporting can be done without a designer.
If it's not broken, fix it until it is
-
Pete O'Hanlon wrote:
It uses XAML so it doesn't have a designer. That wasn't a requirement in your list. To be honest, the XAML is nice and clean. This is the sample Image report:
To me it's assumed that you need a designer. Yes, XAML is nice & clean... and VERY time consuming. For anything other than a VERY simple report it would take all day to get laid out right. I noticed on their site that someone asked for a designer. Nice idea for an add on to the project. I can't see how any serious reporting can be done without a designer.
If it's not broken, fix it until it is
Kevin Marois wrote:
and VERY time consuming
Hmmm. I'm not sure I agree here. I can churn out XAML at a phenomenal rate.
-
Kevin Marois wrote:
and VERY time consuming
Hmmm. I'm not sure I agree here. I can churn out XAML at a phenomenal rate.
I can too. Don't get me wrong. I love XAML But for every little tweak, you would need to stop, compile, run the report (meaning fire up your app, get to the report, run it - OOPS that label isn't aligned right!!! Stop, open XAML, tweak, repeat. With a designer it's one & done.
If it's not broken, fix it until it is
-
I need a reporting tool for use in a WPF app. Requirements: 1. Preferably free 2. The report will probably NOT be too complex, so I don't need anything too complicated. 3. Easy to learn 4. Easy to deploy. Any suggestions? Thanks!
If it's not broken, fix it until it is
If you want a report designer then you could always look at SyncFusion reports[^]. I'm a big fan of SyncFusion now. They have worked hard on the performance of their WPF products, and this really shows.
-
I need a reporting tool for use in a WPF app. Requirements: 1. Preferably free 2. The report will probably NOT be too complex, so I don't need anything too complicated. 3. Easy to learn 4. Easy to deploy. Any suggestions? Thanks!
If it's not broken, fix it until it is