Rank: Newbie Groups: Member
Joined: 12/11/2013 Posts: 8
|
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,338
|
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: Newbie Groups: Member
Joined: 12/11/2013 Posts: 8
|
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!
|