Rank: Advanced Member
Groups: Member
Joined: 2/11/2015
Posts: 122
|
I have a situation where I have a shared folder with limited write permissions, and in this folder my application launches and since the folder is shared we cannot modify or write to the folder reliably.
Unfortunately, the auto-generation of the exe for the EO library is stunted by this, and I'm now required to include the executable int he project so its distributed upon installation, rather than generated.
Is it possible to have a NuGet package, or update the current page, so that it can include the executable in the project automatically?
Or will I be stuck forgetting to upgrade the exe each time I need to update the library?
Thank you!
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi, I am assuming that you meant eowp.exe. You do not have to have that file unless you have this property set to true: http://www.essentialobjects.com/doc/eo.base.runtime.enablelargeaddressspace.aspxIf you do have the above property set to true, then you do need this file. You can override the location of that file through this method: http://www.essentialobjects.com/doc/eo.base.runtime.initworkerprocessexecutable.aspxIf you call the above method, you do not need to include the file in your distribution. The above method will create the exe file. You just have to make sure the folder is writable (you must have somewhere to be writable, otherwise the browser engine won't be able to save cache and cookies). Thanks!
|
Rank: Advanced Member
Groups: Member
Joined: 2/11/2015
Posts: 122
|
So the folder does not have to be the folder containing the rest of the DLLs?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
No. It can be anywhere on your system.
|