Member Avatar for priyamtheone

I'm using Visual Studio 2017. After installing Productivity Power Tools 2017/2019 extension, I can't use the copy operation. The first time I try to copy a line or block of code after installing the extension, Visual Studio generates an error saying:

"Type library exporter encountered an error while processing 'CopyAsHtml.CopyAsHtmlPackage, CopyAsHtml'. Error: Type library exporter encountered an error while processing 'Microsoft.VisualStudio.Shell.Interop.SVsSolutionObject, Microsoft.VisualStudio.Shell.Interop'. Error: Type 'SVsSolutionObject' and type 'SVsSolution' both have the sameUUID."

Next time onwards, whenever I try to copy, Visual Studio generates the error saying:

"Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL))"

When I uninstall Productivity Power Tools 2017/2019, there's no error message and I can copy everything properly. It seems, the problem is with the extension. So, is there a way to fix the problem so that I can use Productivity Power Tools 2017/2019 and not encounter the problem at the same time? Or shall I have to give up using Productivity Power Tools 2017/2019 entirely and continue Visual Studio without it?

Regards

  • 2 Contributors
  • 2 Replies
  • 96 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by priyamtheone

Dani AI

Generated

Short summary: has already tracked the breakage to the Copy As Html piece of Productivity Power Tools and is right that the extension author needs an issue report. The fastest path to a permanent fix is to gather reproducible diagnostics and file a clear bug report so the maintainer can reproduce and patch the conflicting registration/interop behavior.

Diagnostic checklist to attach to a report:

  • Record the exact Visual Studio build (Help > About) and the extension VSIX name/version.
  • Reproduce the fault and capture the Visual Studio activity log by starting VS with devenv /log and saving the produced ActivityLog.xml.
  • Verify extension isolation with devenv /safemode (helps confirm whether an installed extension is involved).
  • If convenient, grab a process dump (Task Manager -> right-click devenv.exe -> Create dump file) at the moment the error shows; include timestamps and the steps you used to reproduce.
  • For advanced troubleshooting, enable assembly-binding logging with the Fusion Log Viewer (fuslogvw) if assembly GUID/registration collisions are suspected. Note: fuslogvw is verbose and should be used temporarily.

When filing the issue on the extension's Marketplace/GitHub page, include: VS build, extension version, step-by-step repro, ActivityLog.xml, and any dump files. Do not attach proprietary source; redact sensitive content. As interim options, check whether an updated extension or Visual Studio update is available, or use an external "copy as HTML" utility until the extension author releases a fix.

Recommended Answers

All 2 Replies

Member Avatar for rproffitt

Such bugs are reported back to the author of these extensions. If folk don't report then the author won't know to fix it.

Member Avatar for priyamtheone

Delving deep into the issue brings across the fact that a sub-component of the Productivity Power Tool extension, named Copy As Html, is breaking the copy/cut operation. Disabling/uninstalling the sub-component solves the problem as per my observation. Though, I'm not sure what other essential operation is deactivated by the disabling of the sub-component.

Got to Tools > Extensions and Update and select the Installed node on the left panel. In the list of extensions in the middle, scroll down to Copy As Html and disable or uninstall it.

commented: Be sure to add that to the git hub bug report. +16
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.