benny1007

@rjmholt I would like to give it a try if I can be pointed in the right direction

wow, how could I go wrong with such concise instructions, thanks. Give me a few days to review and get my head around all the working parts.

If I try and run any of the LanguageService tests I get the following:- Message: ``` System.Management.Automation.CommandNotFoundException : The term 'Get-ExecutionPolicy' is not recognized as the name of a cmdlet,...

ah sorry perhaps I should have been a bit clearer. I was just opening the PowerShellEditorServices project in Visual Studio 2017 and running the tests from Test Explorer.

`Invoke-Build Build Test` doesn't work but `Invoke-Build Test` does but fails tests, this is on the master branch. Total tests: 194. Passed: 188. Failed: 5. Skipped: 1. Test Run Failed.

Yep, `Invoke-Build Build` successfully builds the project. `Invoke-Build Test` returns lots of test failures... ``` Starting test execution, please wait... [xUnit.net 00:00:01.8300459] AsyncDebouncerFlushesAfterInterval [SKIP] Skipped AsyncDebouncerFlushesAfterInterval [xUnit.net 00:00:06.7751709] CorrectlyResolvesPaths(givenPath: "file:///path/wi[th]/squ[are/brackets/",...

I may just delete my fork and re-clone?

If I update the following lines:- PowerShellContext.cs ln 1963 ln 1984 ln 2135 to call 'AddScript' instead of 'AddCommand' all of the tests then run from Visual Studio 2017 test...

> @Benny1007 did you try re-cloning? yeah that was from the clone

would make c# development in vscode a thing, the current formatting configuration for c# in vs-code leaves a lot to be desired.