Rank: Newbie
Groups: Member
Joined: 5/13/2025
Posts: 2
|
The names of the named pipes used (inside EO.Base.dll) for communication with child processes do not take assembly load contexts into account.
Currently, when the names of the named pipes are generated, they use the process id and appdomain id to create a name that is unique across processes and appdomains (though appdomains are no longer relevant in .NET Core).
But if EO components are used from different assembly load contexts inside the same process, that is not taken into account, and the names of the named pipes will conflict with each other, preventing EO components from working correctly.
This scenario (using EO components from different assembly load contexts inside the same process) is important for plugin-based applications running inside 3rd party host applications.
Please let me know if you need any additional information.
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,365
|
Thanks for letting us know. This will be replaced with a GUID in our next build. We will reply here again as soon as the new build is avaliable.
|
Rank: Newbie
Groups: Member
Joined: 5/13/2025
Posts: 2
|
Thanks a lot!
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,365
|
Hi,
We have sent a new build to you through private message. Please take a look and let us know how it goes.
Thanks!
|