I used to run this on a console and deploy the app via VS 2010. adb logcat appname:E appname:I mono:E mono:I mono-stdout:D monodroid-gc:I dalvikvm:D *:F
But since last couple of versions if I do the above after an app is deployed then in order to redeploy the app I have stop this command in the console and close VS 2010, reopen it, deploy the app and then run the command above for app specific logging. I have to restart VS 2010 because even after closing the console logger VS2010 is unable to see the device (must be an issue adb server) and only way to get it to see the device has been to restart it. Due to the hassels mentioned above, I started looking at the Android Device logging window that also does logging. But I have been unable to filter it like I do via the console and end up having to peruse through a lot of unwanted logs to see my app specific logs. Is there a way to a. Get VS to see the device after console logging is stopped b. If not, is there is a way to filter the logging done via the "Android Device Filtering" view in VS2010 If I am doing this wrong, please help me do logging and deploying the recommended way. Thanks -- View this message in context: http://mono-for-android.1047100.n5.nabble.com/VS-2010-Android-Device-Logging-does-not-filter-tp5711416.html Sent from the Mono for Android mailing list archive at Nabble.com. _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
