Rank: Newbie
Groups: Member
Joined: 8/10/2021
Posts: 2
|
Hi,
As a registered user, I've been using the web-browser component for quite a while from NuGet. I use the pre-built "eowp.exe" as part of the application to avoid virus and security scanner issues with RUNDLL or auto-generating the executable.
However, recent versions in NuGet are now delivering an "eowp.,exe" with a different version to that of the main .NET assemblies. This is now causing issues in that the application automatically generates a new one.
For example, with NuGet 22.0.30, the eowp.exe was version "22.0.23" causing the run-time to generate an "eowp.22.0.30.0.exe" file in the user temp, which was then blocked.
This also affects the latest NuGet 22.1.13, except in this case the eowp.exe version is higher rather than lower.
The latest version downloaded from the EO site doesn't seem to have this issue.
Can this be addressed to avoid having to switch back to a local version instead of NuGet?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,070
|
Thanks for bringing this issue to our attention. This has to be an issue in our automated build process. We will look into this and post an update build with the correct version as soon as possible. The pre-build eowp.exe supposes to have the same version number as other .NET assemblies.
|
Rank: Newbie
Groups: Member
Joined: 8/10/2021
Posts: 2
|
Many thanks.
|