Bug 10702 - MonoTouchActivation.app should hook up logging.
Summary: MonoTouchActivation.app should hook up logging.
Status: VERIFIED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Activation ()
Version: 1.0.x
Hardware: PC Mac OS
: Low enhancement
Target Milestone: 1.8.x (VS2013)
Assignee: Dominique Louis
URL:
Depends on:
Blocks:
 
Reported: 2013-02-26 16:17 UTC by Bojan Rajkovic [MSFT]
Modified: 2013-11-15 05:14 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
VERIFIED FIXED

Description Bojan Rajkovic [MSFT] 2013-02-26 16:17:02 UTC

    
Comment 1 Bojan Rajkovic [MSFT] 2013-02-26 16:17:43 UTC
Gah, forgot to make a comment. MonoTouchActivation.app should hook up the CustomLogger interface inside Xamarin.Ide so we can debug its output in cases where customers are having issues using it.
Comment 2 Alan McGovern 2013-10-23 12:47:32 UTC
This app has gone in 1.8 so we can just close this as 'does not apply to 1.8'. I really don't think we care about fixing 1.6 in this case so I'm just closing this.
Comment 3 Mohit Kheterpal 2013-11-15 05:14:19 UTC
Today we have checked this issue with following builds :

VS 2013
MTVS 1.8.365

We are not getting this issue any more due to change in functionality.

Hence closing this issue.