Refactored the VS add-in

visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/Utility.cs

Index: visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/Utility.cs
diff --git a/visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/Utility.cs b/visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/Utility.cs
index 8dcdb02a67074f37c3b15ef69018943edb5e58d3..69eec0fb8072bf2c60dcc1220dd6e3dc836062ea 100644
--- a/visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/Utility.cs
+++ b/visual_studio/NativeClientVSAddIn/NativeClientVSAddIn/Utility.cs
@@ -65,6 +65,25 @@ namespace NativeClientVSAddIn
     }
 
     /// <summary>
+    /// Will print a message to the web server output pane.
+    /// </summary>
+    /// <param name="dte">The main visual studio interface.</param>
+    /// <param name="message">Message to print to the output pane.</param>
+    public static void WebServerWriteLine(DTE2 dte, string message)
+    {
+      try
+      {
+        OutputWindowPane pane = dte.ToolWindows.OutputWindow.OutputWindowPanes.Item(
+            Strings.WebServerOutputWindowTitle);
+        pane.OutputString(message + "\n");
+      }
+      catch (ArgumentException)
+      {

[noelallen1, 2012/08/08 00:22:15]

How can that page not exist yet?  Has it been destroyed?

[tysand, 2012/08/08 04:15:59]

Since this is just a static utility function it can't be sure that the output
pane is created yet (by the Connect class).  In theory it should always be there
though.
On 2012/08/08 00:22:15, noelallen1 wrote:

+        // This exception is expected if the window pane hasn't been created yet.
+      }
+    }
+
+    /// <summary>
     /// Returns all VCConfigurations from the open solution that have the specified platform name.
     /// Note only VC++ projects are checked.
     /// </summary>