Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 4792 [details]
In my application I write a lot of information in the console with Console.WriteLine. Everytime I restart my application, I receive all my log in the console from my previous executions. Now I can't use my console because I must wait 5 minutes each times because it's spamming all the log from the previous executions. This only happens when I start without debugging (ctrl + F5).
The project iPadTest in attachment will show you this problem.
1- Open it with Visual Studio
2- Start without debugging (ctrl + F5)
You will see in the output window of Visual Studio "debug" the log : "I only write one time this log, so why do I see it many times?"
3- Start again without debugging
Now you will see two times the last log
Deleting every log located here "~/Library/Logs/Xamarin/MonoTouchVS" seems to clear the log sent to visual studio at every application launch. But it is pretty annoying to do it everytime...
As of the 1.6.x release (not yet publicly released) this issue is fixed.
The Debug log is cleared on subsequent debug attempts: http://screencast.com/t/2x1KtY34H0Dp
Note: Starting without debugging gives you no output from Console.Writeline, not sure if this is a real difference in the test case or simply an oversight.
Please REOPEN if I have misrepresented the issue, or if you get the 1.6 builds when they are released and your issue has not been fixed.
Today we have checked this issue with following builds :
Now we are getting different logs for every debug session.
screencast : http://screencast.com/t/WiYWhYskUF
Hence closing this issue.