{"push_id":540514505,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"2c08dc1df51a278507297d8cfe27e9515ef9d529","before":"52cad62573237ab0369faef3e51b1e8c5edc7e84","commits":[{"sha":"2c08dc1df51a278507297d8cfe27e9515ef9d529","author":{"email":"78e20a349b4aa247af6f08cfbf42d02a1cf4a8ea@gmail.com","name":"Matt Ward"},"message":"[NuGet] Fix second Package Console opened when creating new solution.\n\nWith check for package updates enabled in Preferences a second Package\nConsole was opened when a new solution was created from a project\ntemplate that added NuGet packages, such as the ASP.NET MVC project\ntemplate. This bug was introduced when the check for updates was\nchanged to run on its own separate thread. This separate thread would\ncreate its own Package Console window to monitor progress before the\noriginal progress monitor that was monitoring NuGet packages being\nadded to the project could be disposed.\n\nNow the second Package Console window is not opened when the check\nfor updates runs after a new solution is created. One side effect is\nthat the Package Console is cleared when the check for updates\nbegins. However if there is an error when installing the NuGet\npackages the check for updates will not be run so the error will\nremain available in the Package Console.","distinct":true,"url":"https://api.github.com/repos/mono/monodevelop/commits/2c08dc1df51a278507297d8cfe27e9515ef9d529"}]}