In-Memory Compilation / Disabling Antivirus problems
Posted: Thu Apr 21, 2016 8:09 am
Hi there,
sometimes we went into heavy troubles when an antivirus manufacture provides new signatures (last Panda Antivirus). When executing a report, csc.exe is used to compile the report into an assembly stored in the %temp% path. Sometimes an antivirus software thinks this assembly is infected and moves/deletes this file which results in an exception when Stimulreports tries to execute the code inside of this assembly. On server systems and/or other security environments (e.g. VirtualUI) there is also the problem, that the user needs special rights to execute the csc.exe.
With the new Roslyn project it is now possible to compile directly into memory without the need to create a file based assembly. I found a nice description here:
http://www.tugberkugurlu.com/archive/co ... ith-roslyn
Would this be a feature for 2016.2?
Kind regards,
Markus
sometimes we went into heavy troubles when an antivirus manufacture provides new signatures (last Panda Antivirus). When executing a report, csc.exe is used to compile the report into an assembly stored in the %temp% path. Sometimes an antivirus software thinks this assembly is infected and moves/deletes this file which results in an exception when Stimulreports tries to execute the code inside of this assembly. On server systems and/or other security environments (e.g. VirtualUI) there is also the problem, that the user needs special rights to execute the csc.exe.
With the new Roslyn project it is now possible to compile directly into memory without the need to create a file based assembly. I found a nice description here:
http://www.tugberkugurlu.com/archive/co ... ith-roslyn
Would this be a feature for 2016.2?
Kind regards,
Markus