|
|
Rank: Newbie
Groups: Member
Joined: 8/30/2019
Posts: 6
|
We cannot deploy EOWP.exe to our customer base because the version check is failing. .NET Version constructor throws an exception on this constructor https://docs.microsoft.com/en-us/dotnet/api/system.version.-ctor?view=netframework-4.8#System_Version__ctor_System_String_Please change your Production version to use Periods instead of Commas. Right click properties of EOWP.exe, production version says 19,2,42,0 instead of 19.2.42.0
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi, EOWP.exe is not a .NET assembly. So you can not use any .NET version checking code on it. You can either exclude the file from your version checking mechanism, or create the file dynamically at runtime using this method: https://www.essentialobjects.com/doc/eo.base.runtime.initworkerprocessexecutable.aspxThanks!
|
|
Rank: Newbie
Groups: Member
Joined: 8/30/2019
Posts: 6
|
Version works on any File. we use all files that support a ProductVersion to ensure our customer has the latest version of dlls and executables. Since we are using WebBrowser with eowp turned on, we need to be able to deploy this file and verify the version is correct. Using "," in the version string breaks with Windows standard.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
We will change this in our next build. In the mean time, you can create EOWP dynamically instead.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 8/30/2019
Posts: 6
|
Thanks! we're manually setting the version to get around the issue, but this will be better long-term
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,218
|
Hi,
This is just to let you know that we have posted a new build that should address this issue. You can download the new build from our download page. Please take a look and let us know how it goes.
Thanks!
|
|