mirror of
https://github.com/Set-OutlookSignatures/Set-OutlookSignatures.git
synced 2026-04-26 10:45:52 +03:00
[GH-ISSUE #84] AngleSharp dependency #28
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Set-OutlookSignatures-Set-OutlookSignatures#28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @panki27 on GitHub (Aug 16, 2023).
Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/84
Originally assigned to: @panki27, @GruberMarkus on GitHub.
After implementing my workaround described in #83, I get another error when trying to set the signature:
So it seems like I'm missing a DLL? Not sure which one or where to get it, though.
Running the script with
-MoveCSSInline $falseworks fine.@GruberMarkus commented on GitHub (Aug 16, 2023):
The message
AUSFÜHRLICH: Das in die Pipeline geschriebene Objekt ist eine Instanz vom Typ "mshtml.HTMLDocumentClass"can be ignored, as this is a verbose message which is of informational character, does not hint to an error, and can not be turned off.The MoveCSSInline error is definitely a bug. I currently can not reproduce it on any of my test systems, but from experience the following code change should solve the problem:
Set-OutlookSignatures.ps1 v4.2.0
Change lines 651-657 from
to
If you can confirm that the code change solves the problem, I will include it in the next hotfix release.
@panki27 commented on GitHub (Aug 16, 2023):
Hi Markus, thanks for the quick reply!
Implementing the suggested change fixes the issue 👍
@GruberMarkus commented on GitHub (Aug 16, 2023):
My pleasure!
I will close this issue. The code (and adopted clean-up code) will be part of the next hotfix release. It is not yet clear when this will be released, but I would like to to wait for the result of issue #83 and release both fixes in the same version.