You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently ship PSScriptAnalyzer as a DLL dependency to PowerShell Editor Services when we release updates to the VS Code extension. We should change our approach to use the user's currently-installed PSScriptAnalyzer module and invoke its cmdlets instead of using it as a C# API.
We might ultimately need some extra logic to only use a version of the module within a certain range in case we need to avoid breaking changes to the cmdlets, though I think that's not extremely likely to happen in the short torm.
I'll try to get this in for 0.6.0 but if I don't have time I'll do it for 0.7.0.
The text was updated successfully, but these errors were encountered:
daviwil
changed the title
Remove bundled PSScriptAnalyzer, use installed copy as cmdlet
Remove bundled PSScriptAnalyzer, use installed module's cmdlet instead
Apr 28, 2016
We currently ship PSScriptAnalyzer as a DLL dependency to PowerShell Editor Services when we release updates to the VS Code extension. We should change our approach to use the user's currently-installed PSScriptAnalyzer module and invoke its cmdlets instead of using it as a C# API.
We might ultimately need some extra logic to only use a version of the module within a certain range in case we need to avoid breaking changes to the cmdlets, though I think that's not extremely likely to happen in the short torm.
I'll try to get this in for 0.6.0 but if I don't have time I'll do it for 0.7.0.
The text was updated successfully, but these errors were encountered: