It appears that My-FyiReporting is the sole active fork of the old (now defunct) FyiReporting, so I've started a new thread to share my findings.
It seems to me that it has great promise if the potential users could be assured of continued development and support.
For those of us wishing to avoid the cost and complexity of full blown reporting options, this simple option may suit us perfectly. It just needs to gain a critical mass of followers to snowball onwards.
I have emailed the project maintainer Peter, and he says, promisingly :
"I am hosting my code https://github.com/majorsilence/My-FyiReporting and hopefully that will encourage some more active development from others.
I will generally only be fixing bugs that affect me or adding features that I need. However patches from others is very much encouraged."
Now, the good news is that it costs nothing to play with it. There are both .MSI and .ZIP downloads at
https://github.com/majorsilence/My-F...ting/downloads
and I unzipped 4.5.0-my-fyi-build-dot-net-4-x86.zip into a test folder and found that it works without installing or registering anything, so it won't work its tentacles into your setup if you're nervous about such things!
The zip file contains 18 files, a collection of .EXE and .DLL along with some config XML files. I'm ignoring the server and map stuff, as I just want to design a report and then make it appear from my vb.net app.
Designer : RdlDesigner.exe
The standalone designer loads the previously loaded report, or has a new report wizard. It looks like this:
Attachment 90315
In the wizard, I kept the default SQL option and dialled in a connection string like :
server=MYSERVER; database=MyTest; Integrated Security=SSPI
- and it connected straight away, and listed the tables and fields. It was easy to write a SELECT query, using a button to copy field names, and as if my magic my report was there, looking like it would suit my requirements perfectly. The report was saved to a .RDL file containing XML as follows-
RdlReader.exe
A report viewer control may be added your VB forms, but there is also a standalone reader. So I have been able to load an RDL file into that and there is my report.
This is looking good, IMHO, I will keep you updated as I go...
Reminder
This is Open Source under the Apache License, Version 2.0 ( http://www.apache.org/licenses/LICENSE-2.0 ) so you can use it in your project and supply it to customers.
Helpful documentation from the original project can be found at http://fyireporting.com/helpv4/
along with Peter's newer wiki at https://github.com/majorsilence/My-FyiReporting/wiki
It seems to me that it has great promise if the potential users could be assured of continued development and support.
For those of us wishing to avoid the cost and complexity of full blown reporting options, this simple option may suit us perfectly. It just needs to gain a critical mass of followers to snowball onwards.
I have emailed the project maintainer Peter, and he says, promisingly :
"I am hosting my code https://github.com/majorsilence/My-FyiReporting and hopefully that will encourage some more active development from others.
I will generally only be fixing bugs that affect me or adding features that I need. However patches from others is very much encouraged."
Now, the good news is that it costs nothing to play with it. There are both .MSI and .ZIP downloads at
https://github.com/majorsilence/My-F...ting/downloads
and I unzipped 4.5.0-my-fyi-build-dot-net-4-x86.zip into a test folder and found that it works without installing or registering anything, so it won't work its tentacles into your setup if you're nervous about such things!
The zip file contains 18 files, a collection of .EXE and .DLL along with some config XML files. I'm ignoring the server and map stuff, as I just want to design a report and then make it appear from my vb.net app.
Designer : RdlDesigner.exe
The standalone designer loads the previously loaded report, or has a new report wizard. It looks like this:
Attachment 90315
In the wizard, I kept the default SQL option and dialled in a connection string like :
server=MYSERVER; database=MyTest; Integrated Security=SSPI
- and it connected straight away, and listed the tables and fields. It was easy to write a SELECT query, using a button to copy field names, and as if my magic my report was there, looking like it would suit my requirements perfectly. The report was saved to a .RDL file containing XML as follows-
Code:
<?xml version="1.0" encoding="UTF-8"?>
<Report xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition" xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<Description>
</Description>
<Author>
</Author>
<PageHeight>11in</PageHeight>
<PageWidth>8.5in</PageWidth>
<DataSources>
<DataSource Name="DS1">
<ConnectionProperties>
<DataProvider>SQL</DataProvider>
<ConnectString>server=MYSERVER; database=MyTest; Integrated Security=SSPI</ConnectString>
</ConnectionProperties>
</DataSource>
</DataSources>
<Width>7.5in</Width>
<TopMargin>.25in</TopMargin>
<LeftMargin>.25in</LeftMargin>
<RightMargin>.25in</RightMargin>
<BottomMargin>.25in</BottomMargin>
<DataSets>
<DataSet Name="Data">
<Query>
<DataSourceName>DS1</DataSourceName>
<CommandText>SELECT field1, field2 FROM table1</CommandText>
</Query>
<Fields> .... etc...A report viewer control may be added your VB forms, but there is also a standalone reader. So I have been able to load an RDL file into that and there is my report.
This is looking good, IMHO, I will keep you updated as I go...
Reminder
This is Open Source under the Apache License, Version 2.0 ( http://www.apache.org/licenses/LICENSE-2.0 ) so you can use it in your project and supply it to customers.
Helpful documentation from the original project can be found at http://fyireporting.com/helpv4/
along with Peter's newer wiki at https://github.com/majorsilence/My-FyiReporting/wiki