Page 1 of 1

Compilation error when viewing and previewing report

Posted: Thu Mar 18, 2021 7:07 am
by vitek.abeln
Hello,

I have updated to the new version of Stimulsoft.Angular.NetCore (2021.2.1). I have tested this on a report which only has some square shapes and some text and I get this error "Compilation error: Preprocessor directives must appear as the first non-whitespace character on a line } expected } expected". I have also tried this with an empty report and I get the same result. In the viewer I only get an error "Something bad happened". Any help is appreciated.

Best regards

Re: Compilation error when viewing and previewing report

Posted: Thu Mar 18, 2021 6:25 pm
by Sergio Museninni
vitek.abeln wrote: Thu Mar 18, 2021 7:07 am Hello,

I have updated to the new version of Stimulsoft.Angular.NetCore (2021.2.1). I have tested this on a report which only has some square shapes and some text and I get this error "Compilation error: Preprocessor directives must appear as the first non-whitespace character on a line } expected } expected". I have also tried this with an empty report and I get the same result. In the viewer I only get an error "Something bad happened". Any help is appreciated.

Best regards
Hello
We could not reproduce this. Please send us a sample on which we will reproduce the issue.
Thank you

Re: Compilation error when viewing and previewing report

Posted: Mon Mar 22, 2021 10:09 am
by vitek.abeln
empty report.mrt
Empty report that causes error.
(2.52 KiB) Downloaded 326 times
Here you go. It is literally an empty report. I guess it does not have much with the report itself but with the designer something not reading properly.

Re: Compilation error when viewing and previewing report

Posted: Tue Mar 23, 2021 7:09 am
by Sergio Museninni
vitek.abeln wrote: Mon Mar 22, 2021 10:09 am empty report.mrt
Here you go. It is literally an empty report. I guess it does not have much with the report itself but with the designer something not reading properly.
Hello
Our technical specialists are already investigating your problem.
Thank you
#3772