In Visual Studio Code when coding classes or commands that reference classes or referencing SMO types the rule TypeNotFound is enforced. The rule is excluded in the file .vscode/analyzersettings.psd1 but it is still enforced. If possible we should not enforce the rule TypeNotFound inside Visual Studio Code.
But, we should still support it in QA tests which uses the same Scrip Analyzer configuration file .vscode/analyzersettings.psd1.
See issue #1771 how the rule should be run on built module only. So this issue and issue #1771 must work in tandem, or we might just have to live with seeing the rule fail in VS Code.
In Visual Studio Code when coding classes or commands that reference classes or referencing SMO types the rule TypeNotFound is enforced. The rule is excluded in the file
.vscode/analyzersettings.psd1but it is still enforced. If possible we should not enforce the rule TypeNotFound inside Visual Studio Code.But, we should still support it in QA tests which uses the same Scrip Analyzer configuration file
.vscode/analyzersettings.psd1. See issue #1771 how the rule should be run on built module only. So this issue and issue #1771 must work in tandem, or we might just have to live with seeing the rule fail in VS Code.