prefer shell vs dos

Author: johnsimons

nservicebus/gateway/troubleshooting.md

@@ -40,21 +40,21 @@ If the gateway is not listening no response will be received.
 
 To clean and recreate the url acl manually run the following commands from an admin console:
 
-```dos
+```shell
 netsh http delete urlacl YourUrl
 netsh http add urlacl url=YourUrl user="YourMachine\EndpointUsername"
 ```
 
 For example
 
-```dos
+```shell
 netsh http delete urlacl http://localhost:25894/MyEndpoint/
 netsh http add urlacl url=http://localhost:25894/MyEndpoint/ user="Machine\MyEndpointServiceAccount"
 ```
 
 To list all urlacls on a machine run
 
-```dos
+```shell
 netsh http show urlacl
 ```
 

nservicebus/hosting/nservicebus-host/installation.md

@@ -10,7 +10,7 @@ When running an endpoint within the context of the Visual Studio debugger, the r
 
 To retrieve the list of available options for the host, run the following at the command line:
 
-```dos
+```shell
 NServiceBus.Host.exe /?
 ```
 
@@ -22,7 +22,7 @@ NServiceBus.Host.exe /?
 
 To install the process as a Windows service, include `/install` as a command line argument to the host. Using `/install` also causes the host to invoke the [installers](/nservicebus/operations/installers.md).
 
-```dos
+```shell
 NServiceBus.Host.exe /install
 [/serviceName:<string>]
 [/displayName:<string>]
@@ -40,7 +40,7 @@ NServiceBus.Host.exe /install
 
 Here is an example of the `/install` command line:
 
-```dos
+```shell
 NServiceBus.Host.exe /install
 /serviceName:"MyPublisher"
 /displayName:"My Publisher Service"
@@ -86,7 +86,7 @@ Configures the name of the endpoint. By default, the endpoint name is the namesp
 
 Configures NServiceBus to scan only the specified assemblies. The `scannedAssemblies` parameter must be provided for each assembly to include. E.g.:
 
-```dos
+```shell
 NServiceBus.Host.exe /install
 /scannedAssemblies:"NServiceBus.Core"
 /scannedAssemblies:"NServiceBus.Host"
@@ -141,18 +141,18 @@ A [host profile](profiles.md) can be specified as the last parameter, e.g. `NSer
 
 To uninstall an endpoint service, call
 
-```dos
+```shell
 NServiceBus.Host.exe /uninstall
 ```
 
 If a service name is specified when installing a service, be sure to pass it to the uninstall command:
 
-```dos
+```shell
 NServiceBus.Host.exe /uninstall  [/serviceName]
 ```
 
 For example:
 
-```dos
+```shell
 NServiceBus.Host.exe /uninstall /serviceName:"MyPublisher"
 ```

nservicebus/hosting/nservicebus-host/profiles.md

@@ -65,13 +65,13 @@ To activate a specific profile, pass the full name of the profile in the command
 
 For example, to run the endpoint with the `Integration` and `PerformanceCounters` profiles:
 
-```dos
+```shell
 .\NServiceBus.Host.exe nservicebus.integration nservicebus.performancecounters
 ```
 
 When installing the host as a Windows Service, the profiles used during installation are saved, and they are used every time the host starts. In order to install the host with the `Production` and `PerformanceCounters` profiles:
 
-```dos
+```shell
 .\NServiceBus.Host.exe /install nservicebus.production nservicebus.performancecounters
 ```
 

nservicebus/hosting/windows-service.md

@@ -16,7 +16,7 @@ related:
 
 When [self-hosting a Windows Service](/samples/hosting/generic-host/), the startup code is in full control of installation. Windows supports these features though the use of the [Service Control tool](https://technet.microsoft.com/en-us/library/cc754599.aspx). For example, a basic install and uninstall commands would be:
 
-```dos
+```shell
 sc.exe create SalesEndpoint binpath= "c:\SalesEndpoint\SalesEndpoint.exe --run-as-service"
 sc.exe delete SalesEndpoint
 ```
@@ -28,7 +28,7 @@ For completeness, here are some other common usages of the Service Control tool:
 
 The Windows Service name can be configured at creation time, as follows:
 
-```dos
+```shell
 sc.exe create [ServiceName] binpath= [BinaryPathName]
 sc.exe create SalesEndpoint binpath= "c:\SalesEndpoint\SalesEndpoint.exe --run-as-service"
 ```
@@ -38,7 +38,7 @@ sc.exe create SalesEndpoint binpath= "c:\SalesEndpoint\SalesEndpoint.exe --run-a
 
 The display name can be configured, at creation time, using the `displayname` argument:
 
-```dos
+```shell
 sc.exe create [ServiceName] displayname= [Description] binpath= [BinaryPathName]
 sc.exe create SalesEndpoint displayname= "Sales Endpoint" binpath= "c:\SalesEndpoint\SalesEndpoint.exe --run-as-service"
 ```
@@ -48,7 +48,7 @@ sc.exe create SalesEndpoint displayname= "Sales Endpoint" binpath= "c:\SalesEndp
 
 The description can be changed, after the Windows Service has been created, using the [sc description](https://technet.microsoft.com/en-us/library/cc742069.aspx) command.
 
-```dos
+```shell
 sc.exe description [ServiceName] [Description]
 sc.exe description SalesEndpoint "Service for hosting the Sales Endpoint"
 ```
@@ -58,7 +58,7 @@ sc.exe description SalesEndpoint "Service for hosting the Sales Endpoint"
 
 The dependencies of a Windows Service can be configured after it has been created using the [sc config](https://technet.microsoft.com/en-us/library/cc990290.aspx) command.
 
-```dos
+```shell
 sc.exe config [ServiceName] depend= <Dependencies(separated by / (forward slash))>
 sc.exe config SalesEndpoint depend= MSMQ/MSDTC/RavenDB
 ```
@@ -81,7 +81,7 @@ The default restart duration is 1 minute when enabling recovery via the Windows
 
 The following example will restart the process after 5 seconds the first time, after 10 seconds the second time and then every 60 seconds. The Restart Service Count is reset after 1 hour (3600 seconds) of uninterrupted work since the last restart.
 
-```dos
+```shell
 sc.exe failure [ServiceName] reset= [seconds] actions= restart/[milliseconds]/restart/[milliseconds]/restart/[milliseconds]
 sc.exe failure SalesEndpoint reset= 3600 actions= restart/5000/restart/10000/restart/60000
 ```
@@ -101,7 +101,7 @@ Open the services window, select the endpoint Windows Service and open its prope
 
 Username and password can be configured at creation time using the `obj` and `password` parameters.
 
-```dos
+```shell
 sc.exe create [ServiceName] obj= [AccountName] password= [Password] binpath= [BinaryPathName]
 sc.exe create SalesEndpoint obj= MyDomain\SalesUser password= 9t6X7gkz binpath= "c:\SalesEndpoint\SalesEndpoint.exe --run-as-service"
 ```
@@ -111,7 +111,7 @@ sc.exe create SalesEndpoint obj= MyDomain\SalesUser password= 9t6X7gkz binpath=
 
 The Windows Service start mode can be configured at creation time using the `start` parameter.
 
-```dos
+```shell
 sc.exe create [ServiceName] start= {auto | demand | disabled} binpath= [BinaryPathName]
 sc.exe create SalesEndpoint start= demand binpath= "c:\SalesEndpoint\SalesEndpoint.exe --run-as-service"
 ```
@@ -121,7 +121,7 @@ sc.exe create SalesEndpoint start= demand binpath= "c:\SalesEndpoint\SalesEndpoi
 
 A Windows Service can be uninstalled using the [sc delete](https://technet.microsoft.com/en-us/library/cc742045.aspx) command.
 
-```dos
+```shell
 sc.exe delete [ServiceName]
 sc.exe delete SalesEndpoint
 ```

nservicebus/security/generating-encryption-keys.md

@@ -48,7 +48,7 @@ snippet: Hex-CSharp
 
 Generates 32 random bytes (256bits) in a base64 encoded output:
 
-```dos
+```shell
 openssl rand -base64 32
 ```
 
@@ -57,7 +57,7 @@ openssl rand -base64 32
 
 Generates 32 random characters (256bits):
 
-```dos
+```shell
 openssl rand 32
 ```
 

persistence/ravendb/uninstalling-v4.md

@@ -25,19 +25,19 @@ As of 2014-10-15, the Platform Installer no longer installs RavenDB Version 2.0
 
 To list the URACLs for that port, from an **Admin** PowerShell run:
 
-```dos
+```shell
 netsh.exe http show urlacl | select-string :8080
 ```
 
 This may return something like the following:
 
-```dos
+```shell
 Reserved URL: http://+:8080/
 ```
 
 Remove it with this command:
 
-```dos
+```shell
 netsh.exe http delete urlacl url=http://+:8080/
 ```
 
@@ -50,6 +50,6 @@ There is one additional cleanup step if the PlatformInstaller was used as the me
 
 The following PowerShell command will list the directory which can be safely deleted.
 
-```dos
+```shell
 dir ("{0}\lib" -f $env:ChocolateyInstall) -Filter *RavenDB* | Select -ExpandProperty FullName
 ```

persistence/upgrades/asp-saga-deduplication.md

@@ -73,7 +73,7 @@ where `<directory>` is the full path of the working directory that the de-duplic
 
 The utility will list saga data classes that it found while scanning the assemblies provided. The list of classes is split into two categories: those classes that have a correlation property and those that do not.
 
-```dos
+```shell
 $ NServiceBus.AzureStoragePersistence.SagaDeduplicator.exe directory=saga operation=Download
 
 Following saga types have correlation properties

servicecontrol/configure-non-privileged-service-account.md

@@ -96,7 +96,7 @@ To run the service this way, the custom service account must have rights to log
 
 For example
 
-```dos
+```shell
 runas /user:MyDomain\MyTestUser cmd.exe
 ```
 
@@ -114,7 +114,7 @@ Once login rights are granted:
  1. Shut down the console session.
  1. Start the service.
 
-```dos
+```shell
 ServiceControl.exe --serviceName=Particular.ServiceControl
 ```
 

servicecontrol/troubleshooting.md

@@ -33,7 +33,7 @@ When adding a ServiceControl instance the configured port number is checked to e
 
 In the event that the service fails to start to check if the configured port (typically port 33333) is available. To do this open up an elevated command prompt and issue the following command:
 
-```dos
+```shell
 netstat -a -b
 ```
 or install and use the provided [ServiceControl Management PowerShell module](https://www.powershellgallery.com/packages/Particular.ServiceControl.Management) cmdlet to check a specific port:

servicepulse/host-config.md

@@ -16,14 +16,14 @@ To change it:
  1. Edit the value of `ImagePath`. The value contains the full path to the ServicePulse.exe and a command line of the URL to use:
 
 The default value for ImagePath is:
-```dos
+```shell
 "C:\Program Files (x86)\Particular Software\ServicePulse\ServicePulse.Host.exe" --url="http://localhost:9090"
 ```
 
 Change the value after `--url=` and restart the service.
 
 It may be necessary to reserve the new URL for the account being used to run ServicePulse. For example, to reserve port 9090 for all users:
-```dos
+```shell
 netsh http add urlacl url=http://+:9090/ user=Everyone
 ```