<filename>export_old/issues/netoffice_issue_17986.json
{
  "WorkItem": {
    "AffectedComponent": {
      "DisplayName": "",
      "Name": ""
    },
    "AssignedTo": "",
    "ClosedBy": "",
    "ClosedComment": "",
    "CommentCount": 1,
    "Custom": "",
    "Description": "Right now, the DebugConsole class has options to log to the console, file or memorylist.\nCould you please add 'Trace' as an option which logs a message using the .NET framework trace logging system.\nA call to System.Diagnostics.Trace.WriteLine(message) will do fine.\n \nI request this because it is the most easy way to find problems when developing Add-Ins for us (there is no console available for an add-in). \nBy default,  System.Diagnostics.Trace.WriteLine, messages are written to the Windows debug output. Those messages are displayed in the Visual Studio debug output window in debug mode, and can also be shown using the sysinternals 'DebugView' tool.\nBy using the app.config,  the user can even log the trace output to other outputs.\n \nThank you for this great product, much much better than VSTO!",
    "HtmlDescription": "Right now, the DebugConsole class has options to log to the console, file or memorylist.<br />\nCould you please add 'Trace' as an option which logs a message using the .NET framework trace logging system.<br />\nA call to System.Diagnostics.Trace.WriteLine(message) will do fine.<br />\n <br />\nI request this because it is the most easy way to find problems when developing Add-Ins for us (there is no console available for an add-in). <br />\nBy default,  System.Diagnostics.Trace.WriteLine, messages are written to the Windows debug output. Those messages are displayed in the Visual Studio debug output window in debug mode, and can also be shown using the sysinternals 'DebugView' tool.<br />\nBy using the app.config,  the user can even log the trace output to other outputs.<br />\n <br />\nThank you for this great product, much much better than VSTO!<br />\n",
    "PlainDescription": "Right now, the DebugConsole class has options to log to the console, file or memorylist.\nCould you please add 'Trace' as an option which logs a message using the .NET framework trace logging system.\nA call to System.Diagnostics.Trace.WriteLine(message) will do fine.\n \nI request this because it is the most easy way to find problems when developing Add-Ins for us (there is no console available for an add-in). \nBy default,  System.Diagnostics.Trace.WriteLine, messages are written to the Windows debug output. Those messages are displayed in the Visual Studio debug output window in debug mode, and can also be shown using the sysinternals 'DebugView' tool.\nBy using the app.config,  the user can even log the trace output to other outputs.\n \nThank you for this great product, much much better than VSTO!\n",
    "LastUpdatedBy": "SebastianDotNet",
    "LastUpdatedDate": "2013-06-14T09:33:16.377+02:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "netoffice",
    "ReportedBy": "Piet123",
    "ReportedDate": "2012-05-04T08:43:14.603+02:00",
    "CanContactReportedByUser": false,
    "Status": {
      "Name": "Resolved",
      "Id": 7
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Please add 'Trace' ConsoleMode to DebugConsole",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 17986,
    "HasUserVoted": false
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "Trace is available in the updated 1.5.1 RC\r\n\r\n*have a nice day",
      "PostedBy": "SebastianDotNet",
      "PostedDate": "2012-05-04T19:15:07.81+02:00",
      "WorkItemId": 17986,
      "Id": 203047
    }
  ],
  "CanDeleteWorkItem": true,
  "CanDeleteComments": true
}