Hello, the performance/reability has the same problems with the official repo. I'm trying it on my local computer.
Sadly, one of the plus to jsreport is the ability to use as many report templates with the .net without paying for it.
Posts made by skayablars
-
RE: reliability, performance, deployment and fw
-
reliability, performance, deployment and fw
Hello,
I want to use the webserver option to have a self hosted jsreport studio. But I'm worried about the following points:
Realibility of the platform because when I run in local sometimes it runs, sometimes not. Is this problem a common occurrence?
Rendering performance: With the samples sometimes the invoice report give me a timeout exception and is a fairly simple report. The orders report always give me a timeout exception. The performance depends of the machine power? Are there other things that I have to take in consideration (my pc is not the greatest).
Deployment: Maybe this is offtopic, I don't have experience deploying c# apps, I have to run a console project that will run the webserver with jsreport studio? How I change the configuration so it use the production enviorement. I'm not asking for concrete solutions but a head start will be appreciated.
Framework: I don't know if is just my thoughs but the webserver solution works better with .net core. I know that the libraries use .net standard so it shouldn't be a problem using it with full .net.
Thank you for your time
-
RE: An unhandled exception occurred while processing the request.
This is happening to me, the tutorial seems fine but when I try to implement it on my own it fails.
-
Browser api with .net server
Hello,
I read that I can host my own jsreport studio server and have x templates without any kind of limitation. Can I use the browser api to point to the server and still don't have any kind of limitation or the browser api only works for free (up to 5 templates) or payment subscriptions of js report.
If It's doable where I can put my custom host? Didn't see any documentation pointing this in the api section.