Added shell command for ps1 scripts

Author: Bart Koelman

.github/CONTRIBUTING.md

@@ -60,8 +60,8 @@ Please follow these steps to have your contribution considered by the maintainer
 
 We use [CSharpGuidelines](https://csharpcodingguidelines.com/) as our coding standard (with a few minor exceptions). Coding style is validated during PR build, where we inject an extra settings layer that promotes various suggestions to warning level. This ensures a high-quality codebase without interfering too much when editing code.
 You can run the following [PowerShell scripts](https://github.com/PowerShell/PowerShell/releases) locally:
-- `inspectcode.ps1`: Scans the code for style violations and opens the result in your web browser.
-- `cleanupcode.ps1` Reformats the entire codebase to match with our configured style.
+- `pwsh inspectcode.ps1`: Scans the code for style violations and opens the result in your web browser.
+- `pwsh cleanupcode.ps1`: Reformats the entire codebase to match with our configured style.
 
 Code inspection violations can be addressed in several ways, depending on the situation:
 - Types that are reported to be never instantiated (because the IoC container creates them dynamically) should be decorated with `[UsedImplicitly(ImplicitUseKindFlags.InstantiatedNoFixedConstructorSignature)]`.

README.md

@@ -122,7 +122,7 @@ dotnet build
 Running tests locally requires access to a PostgreSQL database. If you have docker installed, this can be propped up via:
 
 ```bash
-run-docker-postgres.ps1
+pwsh run-docker-postgres.ps1
 ```
 
 And then to run the tests:
@@ -134,5 +134,5 @@ dotnet test
 Alternatively, to build and validate the code, run all tests, generate code coverage and produce the NuGet package:
 
 ```bash
-Build.ps1
+pwsh Build.ps1
 ```

docs/request-examples/README.md

@@ -15,5 +15,5 @@ curl -s http://localhost:14141/api/books
 [!code-json[RESPONSE](003_GET_Books-including-Author_Response.json)]
 ```
 
-3. Run `./generate-examples.ps1`
-4. Verify the results by running `docfx --serve`
+3. Run `pwsh ../generate-examples.ps1`
+4. Verify the results by running `pwsh ../build-dev.ps1`