{"action":"opened","issue":{"url":"https://api.github.com/repos/rubberduck-vba/Rubberduck/issues/737","labels_url":"https://api.github.com/repos/rubberduck-vba/Rubberduck/issues/737/labels{/name}","comments_url":"https://api.github.com/repos/rubberduck-vba/Rubberduck/issues/737/comments","events_url":"https://api.github.com/repos/rubberduck-vba/Rubberduck/issues/737/events","html_url":"https://github.com/rubberduck-vba/Rubberduck/issues/737","id":98501426,"number":737,"title":"Logging of the main project","user":{"login":"zippy1981","id":146930,"avatar_url":"https://avatars.githubusercontent.com/u/146930?v=3","gravatar_id":"","url":"https://api.github.com/users/zippy1981","html_url":"https://github.com/zippy1981","followers_url":"https://api.github.com/users/zippy1981/followers","following_url":"https://api.github.com/users/zippy1981/following{/other_user}","gists_url":"https://api.github.com/users/zippy1981/gists{/gist_id}","starred_url":"https://api.github.com/users/zippy1981/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zippy1981/subscriptions","organizations_url":"https://api.github.com/users/zippy1981/orgs","repos_url":"https://api.github.com/users/zippy1981/repos","events_url":"https://api.github.com/users/zippy1981/events{/privacy}","received_events_url":"https://api.github.com/users/zippy1981/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-01T02:59:10Z","updated_at":"2015-08-01T02:59:10Z","closed_at":null,"body":"The parser uses NLog. There is no logging in the main addin solution. I propose (and will provide a patch for) the following:\r\n\r\n* Nlog be configured for the main addin. It will write to a file for all severity and the event log for error severity\r\n* A new event source be created in the application event log called RubberDuck.\r\n* The installer will create this event source\r\n* When one of the toolbox windows fails to initialize, the entire Exception details will be written to nlog at error level\r\n* When the addin fails to initialize, the fill exception will be written to the event log\r\n* I'll add some verbose messages (which won't be written anywhere by default) for all the tooltops being intiialized and long running actions starting and stopping for profiling purposes"}}