Actually, the way I have implemented it right now is that the console application acting as jsreport web server has it's working directory pointing to the app_data folder in the web application, and I have removed the reference to console application from the web application. This involves though a manual step in including the jsreport files in the web application project.

This could be changed so that our release process copies the files to a configured common known location.

I've tried it out and it works just fine, thank you!

Thanks for your reply.

I have tried to use the RunInDirectory() method but it makes no difference when creating the local reporting service AsUtility(). It does work when AsWebServer() is used.

I've looked in to the jsreport.Local project and I can see that the directory field (_cwd) is not used when creating the local reporting service.

        public LocalWebReporting AsWebServer()
        {
            ...

            return new LocalWebReporting(_binary, _cwd, _cfg);
        }
        public LocalUtilityReporting AsUtility()
        {
            ...

            return new LocalUtilityReporting(_binary, _cfg);
        }      

I've set up pdf generation according to the .Net local report example found at https://jsreport.net/learn/dotnet-local#locally-stored-templates. The console application is referenced by a web project and the jsreport resources are copied to the bin/jsreport folder as expected. I run jsreport as web server in the console application and as utility in the web application.

The issue that I have is that every time a report is generated the files (reports, schedules, settings, tasks) in bin/jsreport/data/ folder are updated which causes the application domain to recycle.

I've tried to move the jsreport folder outside the bin folder but couln't congfigure jsreport to find the new location.

Is there any way to achieve this.

Thanks in advance!