|
|
Rank: Member
Groups: Member
Joined: 12/11/2013
Posts: 10
|
Hi Team,
We have Screen resolution issue with EO.WebBrowser version 22.2.79.0. Please find more details below
Feature Overview:
Our application have functionality which is available in Add-in of Microsoft Word and PowerPoint, where users can capture a screenshot of a specific section of a report. This captured screenshot is dynamic—it automatically updates upon clicking the "Refresh" button, reflecting any changes made to the underlying report.
Steps to Reproduce the Issue:
On System 1 with a screen resolution of 1920x1080, capture a specific area of a report.
On System 2 with a different screen resolution (4K), open the same report in Edit Mode.
Observed Issue:
The area captured in Step 1 on System 1 does not align correctly when the same report is opened on System 2. The selected screenshot region appears distorted or shifted, likely due to the difference in screen resolution.
Expected Behavior:
The captured area should remain consistent and maintain its relative position and size across different screen resolutions, ensuring a seamless experience when accessing reports from various devices.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,349
|
Hi,
Please update to the current version and see if it resolves the issue for you. This does appear to be an issue that was fixed in build 2023.1.21.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 12/11/2013
Posts: 10
|
Hi Team,
After upgrading EO.WebBrowser from version 22.2.79.0 to 25.1.35.0 via Manage NuGet Packages, we started encountering the following installation error when running our Microsoft Word Add-in (C# project).
This issue does not occur when using version 22.2.79.0.
We are currently using Microsoft Visual Studio 2010 Tools for Office Runtime (x64), version 10.0.60910.
Questions:
1.Is it necessary to upgrade to a specific version of Microsoft Visual Studio Tools for Office (VSTO) to resolve this issue?
2.Can you please provide the steps to resolve the installation error encountered when running the C# Word Add-in project?
Please find Exception Details below:
Exception reading manifest from file:///C:/User/UserName/source/repos/ProjectName/DebugBuild/ProjectName.WordClient.dll.manifest: the manifest may not be valid or the file could not be opened.
Name:
From: file:///C:/Users/UserName/source/repos/ProjecName/DebugBuild/ProjecName.WordClient.vsto
************** Exception Text **************
System.Deployment.Application.InvalidDeploymentException: Exception reading manifest from file:///C:/Users/UserName/source/repos/ProjecName/DebugBuild/ProjecName.WordClient.dll.manifest: the manifest may not be valid or the file could not be opened. ---> System.Deployment.Application.InvalidDeploymentException: Parsing and DOM creation of the manifest resulted in error. Following parsing errors were noticed:
-HRESULT: 0x80070c81
Start line: 0
Start column: 0
Host file: ---> System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x80070C81
at System.Deployment.Internal.Isolation.IsolationInterop.CreateCMSFromXml(Byte[] buffer, UInt32 bufferSize, IManifestParseErrorCallback Callback, Guid& riid)
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
--- End of inner exception stack trace ---
at System.Deployment.Application.Manifest.AssemblyManifest.LoadCMSFromStream(Stream stream)
at System.Deployment.Application.Manifest.AssemblyManifest..ctor(FileStream fileStream)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- End of inner exception stack trace ---
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.GetManifests(TimeSpan timeout)
at Microsoft.VisualStudio.Tools.Applications.Deployment.ClickOnceAddInDeploymentManager.InstallAddIn()
Troubleshooting Steps we Performed:
Verified the Manifest File
1.Checked the file at:
C:/Users/UserName/source/repos/ProjectName/DebugBuild/ProjectName.WordClient.dll.manifest
Confirmed that it is a valid XML file.
2.Deleted the DebugBuild Folder
Removed the entire DebugBuild directory to eliminate any stale or corrupted build artifacts.
3.Cleaned and Rebuilt the Project
Performed a clean and rebuild of the solution to regenerate all output files, including the manifest.
Despite these steps, the issue persists
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,349
|
Hi,
This has to be a reference issue. When you switch to a new version, the following common errors could occur:
1. If your ProjecName.WordClient.dll references our DLLs and you switched to a newer version when you build your ProjecName.WordClient.dll, then ProjecName.WordClient.dll will look for the new version of our DLLs. If these DLLs are not found or the wrong version (such as the old version) were found, then you may get an error;
2. If your ProjectName.WordClient.dll uses another DLL and that other DLL still references to the old version, then that DLL may looks for the old DLLs but now the new ones are there. Again you will get an error;
In short, it comes down to reference matches actually DLLs. To upgrade to a new version you must do both: update your project reference and then update the actual DLLs files and they must match. If you have done both properly then you should not have any issues.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 12/11/2013
Posts: 10
|
Hi Team,
We recently upgraded the EO.WebBrowser package from version 22.2.79.0 to 25.1.35.0, and are encountering regression issues in our Office Client Add-in (specifically for Microsoft Word and PowerPoint) after the upgrade.
Issue Description
Post-upgrade, the following errors are occurring during standard operations:
"Operation Failed Adding Report" via our Add-in,
"Operation Failed Editing Report" via our Add-in,
Other core functionalities are also impacted.
Important Note: These issues do not occur when the Add-in is launched with Administrator privileges.
Observed Size Increase:
We also noticed a significant increase in the size of the our Office Client executable:
Before upgrade (v22.2.79.0): 119,720 KB
After upgrade (v25.1.35.0): 155,026 KB
Size increase: 35,306 KB
This increase size of our Office Client executable is due to increase in EO dll's size with latest version. Please find the below EO dll, xml files.
1.EO.Base.dll
2.EO.Base.xml
3.EO.WebBrowser.dll
4.EO.WebBrowser.xml
5.EO.WebBrowser.WinForm.dll
6.EO.WebBrowser.WinForm.xml
7.EO.WebEngine.dll
8.EO.WebEngine.xml
We compared the installer and folder contents before and after the EO.WebBrowser upgrade, including all DLLs, and found no differences.
Upgrade Steps Performed:
1.Identified all projects referencing EO.WebBrowser.
2.Upgraded all references from 22.2.79.0 to 25.1.35.0 via NuGet.
3.Cleaned and rebuilt the solution — encountered build errors due to deprecated APIs.
4.Replaced deprecated methods with their recommended alternatives:
a. Replaced QueueScriptCall() with QueueScriptTask()
QueueScriptCall() is no longer supported. We updated to QueueScriptTask() for asynchronous script execution, which ensures scripts run when the JavaScript context is ready.
b. Replaced EO.WebEngine.BrowserOptions with EO.WebEngine.WebViewOptions
BrowserOptions is deprecated. We migrated to WebViewOptions, as recommended for configuring web view settings.
5.Updated the EO.WebBrowser for .NET license key in the codebase for the 2025 release.
Request
We would appreciate your help in identifying and resolving the regression issues described above. we request your assistance with high priority.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,349
|
Hi,
"Operation Failed Adding Report" is not an error message from our code, it appears to be your error message. We can't troubleshoot an error in our code based on error message from your code. You have to trace the error back to our code first. In another word, you need to find out exactly what failed in our library that triggered your code to display that error message. Once you find out that, we will then try to find out why it failed in our library. For example, if you call our library and got an exception, then please post the exception error message and stack trace, we will then go from there.
As for the library size, it did indeed increase in size. Our product is based on Google's Chromium browser engine. The Chromium browser engine has grown in size throughout the years. As a result, our library size grew as well.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 12/11/2013
Posts: 10
|
Hi Team,
Yes, we are encountering some runtime errors in our codebase. However, the same codebase works without any issues when using the EO.WebBrowser package version 22.2.79.0. These errors only appear after upgrading to version 25.1.35.0.
The only changes we made in our code, as mentioned in the previous post, are in steps 4 and 5:
4. Replaced deprecated methods with their recommended alternatives:
a. Replaced QueueScriptCall() with QueueScriptTask()
QueueScriptCall() is no longer supported. We updated it to QueueScriptTask() for asynchronous script execution, which ensures that scripts run when the JavaScript context is ready.
b. Replaced EO.WebEngine.BrowserOptions with EO.WebEngine.WebViewOptions
BrowserOptions is deprecated. We migrated to WebViewOptions as recommended for configuring WebView settings.
Are there any other methods or components we need to update for compatibility with version 25.1.35.0, aside from the changes mentioned above?
We appreciate your response.
Thanks!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,349
|
Hi,
You can't just ignore what we tell you to do and repost the same thing and expect a different answer. You MUST follow our instructions in order to move forward. If you have any questions regarding our previous reply, please feel free to ask. Our last question was:
Exactly what failed in our library that triggered your code to display that error message
So you have to follow through on that first.
Thanks!
|
|