Resolve compiler warnings in Protocol project

This change makes some spot fixes to alleviate compiler warnings that were being produced in the Protocol project.

Author: daviwil

src/PowerShellEditorServices.Protocol/MessageProtocol/Channel/NamedPipeClientChannel.cs

@@ -12,7 +12,6 @@ namespace Microsoft.PowerShell.EditorServices.Protocol.MessageProtocol.Channel
     public class NamedPipeClientChannel : ChannelBase
     {
         private string pipeName;
-        private bool isClientConnected;
         private NamedPipeClientStream pipeClient;
 
         public NamedPipeClientChannel(string pipeName)

src/PowerShellEditorServices.Protocol/MessageProtocol/MessageDispatcher.cs

@@ -18,7 +18,6 @@ public class MessageDispatcher
         #region Fields
 
         private ChannelBase protocolChannel;
-        private AsyncQueue<Message> messagesToWrite;
         private AsyncContextThread messageLoopThread;
 
         private Dictionary<string, Func<Message, MessageWriter, Task>> requestHandlers =

src/PowerShellEditorServices.Protocol/Server/DebugAdapter.cs

@@ -113,7 +113,12 @@ protected async Task HandleConfigurationDoneRequest(
             // launch request.
             if (this.isLaunchRequestComplete)
             {
-                this.LaunchScript(requestContext);
+                // The script needs to be launched asynchronously but we
+                // don't need to wait for it to complete.  Store the task
+                // in a variable to avoid the compiler warning.
+                var unusedTask =
+                    this.LaunchScript(requestContext)
+                        .ConfigureAwait(false);
             }
 
             this.isConfigurationDoneRequestComplete = true;
@@ -173,7 +178,12 @@ protected async Task HandleLaunchRequest(
             // configurationDone request.
             if (this.isConfigurationDoneRequestComplete)
             {
-                this.LaunchScript(requestContext);
+                // The script needs to be launched asynchronously but we
+                // don't need to wait for it to complete.  Store the task
+                // in a variable to avoid the compiler warning.
+                var unusedTask =                
+                    this.LaunchScript(requestContext)
+                        .ConfigureAwait(false);
             }
 
             this.isLaunchRequestComplete = true;