Hi,
There is no additional downside with EnableEOWP turned on beside the file eowp.exe (or any alternative file name you choose) must be created on the customer's system. There are a few different scenarios:
1. If you only set EnableEOWP to true, then the file will be automatically created under user's temp directory --- this again can trigger false alarms from AntiVirus application. It can also cause curious customers to wonder what this process is when they see it in process manager;
2. Alternatively, you can call this method to dynamically create the file with any name/location you choose:
https://www.essentialobjects.com/doc/eo.base.runtime.initworkerprocessexecutable.aspxThis has the benefit of creating the file in a location you choose with the name you choose. For example, instead of creating the file as eowp.exe, it can be created as YourAppChildProcess.exe, which would make it obviously to your customer that this is a part of your application.
Since this method still dynamically creates exe file at runtime, which is a pattern often used by malicious application, it may still trigger false alarm from not so advanced security software/policy;
3. The best approach is to copy eowp.exe from our installation folder, rename it to the name you wish to use and then include it with your distribution. You can then call the same Runtime.InitWorkerProcessExecutable method to notify EO library the location/name of this file. This will avoid the shortcoming of both option 1 and option 2. However you will need to use the latest build in order to use this option. InitWorkerProcessExecutable does exist in early versions, but in early versions, it will always overwrite the file, thus still have the shortcoming of option 2;
Hope this clears thing up for you. Please feel free to let us know if you have any more questions.
Thanks!