Method not found exception occurs when analyze DSC Resource

[mkht]

It seems to have occurred from 1.14.0

PS C:\Users\Administrators> Invoke-ScriptAnalyzer -Path "C:\Users\Administrators\Desktop\TestRsc" -Recurse
Invoke-ScriptAnalyzer : Method not found: 'System.Collections.Generic.List`1<Microsoft.Management.Infrastructure.CimCla
ss> Microsoft.PowerShell.DesiredStateConfiguration.Internal.DscClassCache.ImportClasses(System.String, System.Tuple`2<S
ystem.String,System.Version>, System.Collections.ObjectModel.Collection`1<System.Exception>)'.
発生場所 行:1 文字:1
+ Invoke-ScriptAnalyzer -Path "C:\Users\Administrators\Desktop\TestRsc" -Recurse
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (C:\Users\Administrators\...IISWebsite.psm1:String) [Invoke-ScriptAnalyzer]、Mis
    singMethodException
    + FullyQualifiedErrorId : RULE_ERROR,Microsoft.Windows.PowerShell.ScriptAnalyzer.Commands.InvokeScriptAnalyzerComm
   and

[kapilmb]

Can you provide me the output of [System.Environment]::OSVersion and $PSVersionTable ?

[mkht]

Thanks for your reply.

PS C:\Users\Administrator> [System.Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.14393.0 Microsoft Windows NT 10.0.14393.0


PS C:\Users\Administrator> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.14393.1198
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.1198
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

And I attach the DSC resource and transcript-log used for the test.
TestFiles.zip

[kapilmb]

Thanks for the information and the resource file. From preliminary investigation, this is not a v1.14.0 issue. You can repro this even using v1.13.0. It seems that this error starts appearing after the latest updates to windows but I will need more time to get the root of the issue. In the meantime, a workaround would be run PSScriptAnalyzer on the latest version of PowerShell core, which doesn't seem to have this issue.

[kapilmb]

Fixed in #801