GeezerVison

Had to make the initialization of the analyzer optional as it was clobbering the settings that had been created in the formatter

Hosting seems to work, starting to work on nuget packaging

…nalyzer, CommandCache, and Helper

Had to make the initialization of the analyzer optional as it was clobbering the settings that had been created in the formatter

Hosting seems to work, starting to work on nuget packaging

…nalyzer, CommandCache, and Helper

…lyzer into hosting

There really isn't a good way to do this as the underlying apis aren't really thread safe, but we can do _something_ to the hosted analyzer
If someone is using both the hosted analyzer and the module there may be some unexpected behaviors but doing something is probably better than doing nothing.

Disposing the helper seems to cause downstream problems.
Add async calls to the analyzer

Add a simple tostring method to the HostedAnalyzer

This will check to be sure that we can actually using the nupgk in a project
update the version to 1.18.4

Add tests for the api and in the reference assembly

Change the apis which allow adding settings to return the settings object so they can be chained

Change the order of parameters to make them the same.
remote extraneous documentation xml in Get-ScriptAnalyzerRule cmdlet
Fix test to match new parameter order

Christoph Bergmeister (bergmeister) left a comment

…lyzer into hosting