as malicious, because "reflective code loading" can be used to execute a payload while avoiding some forms of malware detection.
I was able to work around this for myself by removing this line and replacing references to the $ColorType and $ColorTranslator variables with [System.Drawing.Color] and [System.Drawing.ColorTranslator]. See commit ed72492 in my fork. However, this solution fails 18 tests with messages like Unable to find type [System.Drawing.Color], presumably because the System.Drawing assembly is not part of .NET Core/5/6 except via NuGet packages.
It would be nice to get something like this upstreamed, so that I can install future updates without having to modify them. I am not sure whether it is possible (or desirable) to have a NuGet dependency that would allow this to work, or whether there might be another solution that would work better.
System Details
Issue Description
Certain (perhaps overzealous) antivirus software flags the line
as malicious, because "reflective code loading" can be used to execute a payload while avoiding some forms of malware detection.
I was able to work around this for myself by removing this line and replacing references to the
$ColorTypeand$ColorTranslatorvariables with[System.Drawing.Color]and[System.Drawing.ColorTranslator]. See commit ed72492 in my fork. However, this solution fails 18 tests with messages likeUnable to find type [System.Drawing.Color], presumably because theSystem.Drawingassembly is not part of .NET Core/5/6 except via NuGet packages.It would be nice to get something like this upstreamed, so that I can install future updates without having to modify them. I am not sure whether it is possible (or desirable) to have a NuGet dependency that would allow this to work, or whether there might be another solution that would work better.