Creating reports and dashboards | Stimulsoft community forum
Reporting tool and data analytics tools for creating reports and dashboards in ASP.NET, ASP.NET MVC, .NET Core, Blazor, Angular, PHP, Python, WPF, JavaScript, and Java applications.
I'm upgrading your product from 2015.2 to 2016.1. I'm wondering if the upgrade is totally transparent or if I should adapt some parts of the project to make it working fine.
All code should compile from the box without any restrictions. All reports should work as aspected.
Please contact us if you face any problem with upgrading.
I installed the new executables and I upgraded the dlls's and it seemed that all was running fine. But I have 2 problems.
When I execute reports that has a Oracle connection, it dos not recover any data. Report is executed but it seems that the connection is not working fine. Should I adapt any configuration on the reports? The other problem is that I cannot execute the Designer, I getn error [StiMobileDesigner is not defined].
Sorry for missing that, but the problem is that is not founding the DesignerEvnet on the controller. It seems that is not parsing well the url but, this has not changed on my upgrade. This is my configurations
Thanks for the help. I made a sample project with the same configuration, and I succeed on getting the Editor working. That's weird for me, since both projects has been configured exactly the same, the only difference is that the old project had the previous version installed. May I unregister or delete assemblies for older versions prior to upgrade my project? I can send you what I created as a sample project for you, but the error isn't reproduced, it has been solved. If this is profitable for you, I can send you.
While I'm waiting for your answer, I'll retry to figure out why the upgraded project is failing on building correct request to find actions on the server side.
I debugged everythig again, and the problem came to the surface relatively quickly. I guess it's something related to my project configuration, as it's relatively "old" and the routing configuration is a little bit tricky.
So, you can consider this issue as solved. Many thanks for the brilliant and quick support.