Fix for issue #123, wildcard chars in script path prevent breakpoints from working.

Once I got breakpoints to be able to set for files like foo[1].ps1 and foo][.ps1 I noticed that the script named foo][.ps1 would not execute at all!! You get an error saying something like the specified wildcard character pattern is not valid.  FWIW ISE fails with this same message.  So PSES has one up on ISE.  :-)

Author: rkeithhill

src/PowerShellEditorServices/Debugging/DebugService.cs

@@ -56,6 +56,16 @@ public DebugService(PowerShellContext powerShellContext)
 
         #region Public Methods
 
+        /// <summary>
+        /// Returns the passed in path with the [ and ] wildcard characters escaped.
+        /// </summary>
+        /// <param name="path">The path to process.</param>
+        /// <returns>The path with [ and ] escaped.</returns>
+        public static string EscapeWilcardsInPath(string path)
+        {
+            return path.Replace("[", "`[").Replace("]", "`]");
+        }
+
         /// <summary>
         /// Sets the list of breakpoints for the current debugging session.
         /// </summary>
@@ -77,9 +87,13 @@ public async Task<BreakpointDetails[]> SetBreakpoints(
 
             if (lineNumbers.Length > 0)
             {
+                // Fix for issue #123 - file paths that contain wildcard chars [ and ] need to
+                // quoted and have those wildcard chars escaped.
+                string escapedScriptPath = EscapeWilcardsInPath(scriptFile.FilePath);
+
                 PSCommand psCommand = new PSCommand();
                 psCommand.AddCommand("Set-PSBreakpoint");
-                psCommand.AddParameter("Script", scriptFile.FilePath);
+                psCommand.AddParameter("Script", escapedScriptPath);
                 psCommand.AddParameter("Line", lineNumbers.Length > 0 ? lineNumbers : null);
 
                 resultBreakpoints =

src/PowerShellEditorServices/Session/PowerShellContext.cs

@@ -435,8 +435,13 @@ public async Task<IEnumerable<object>> ExecuteScriptString(
         /// <returns>A Task that can be awaited for completion.</returns>
         public async Task ExecuteScriptAtPath(string scriptPath)
         {
+            // If we don't escape wildcard characters in the script path, the script can
+            // fail to execute if say the script name was foo][.ps1.
+            // Related to issue #123.
+            string escapedScriptPath = DebugService.EscapeWilcardsInPath(scriptPath);
+
             PSCommand command = new PSCommand();
-            command.AddCommand(scriptPath);
+            command.AddCommand(escapedScriptPath);
 
             await this.ExecuteCommand<object>(command, true);
         }