Bug 60590 - Can not see full exception when component rendering failed
Summary: Can not see full exception when component rendering failed
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS Designer ()
Version: 4.7.0 (15.4)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-11-09 11:24 UTC by Sergei
Modified: 2018-01-29 21:18 UTC (History)
5 users (show)

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

Screenshot (34.26 KB, image/png)
2017-11-09 11:24 UTC, Sergei

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:

Description Sergei 2017-11-09 11:24:41 UTC
Created attachment 25618 [details]

VS doesn't wrap lines in error message, so I can see only beginning of each line. See attached screenshot.
Comment 1 Sergei 2017-11-09 11:25:35 UTC
Horizontal scrolling doesn't work too.
Comment 2 John Miller [MSFT] 2017-12-05 20:31:37 UTC
Hi Sergei,

Would you be able to include your version information, logs and a sample that reproduces an error message like that? 

You can grab the logs from the Help > Xamairn > Zip Xamarin Logs after that issue happens. The version info is in Help > About Visual Studio > Copy Information. Thanks!
Comment 3 John Miller [MSFT] 2018-01-29 21:18:17 UTC
Because we have not received a reply to our request for more information, we are marking this issue as RESOLVED→NORESPONSE. If you are still encountering this issue on the latest Visual Studio 15.6 Preview 3 version, please don’t hesitate to reopen the ticket with the requested information. Thanks!