Bug 9911 - Connection to the layout renderer failed.
Summary: Connection to the layout renderer failed.
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: Designer ()
Version: 4.4.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2013-01-30 12:29 UTC by Allie Miller
Modified: 2013-01-31 11:27 UTC (History)
1 user (show)

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


Attachments
Output (35.20 KB, image/png)
2013-01-30 12:29 UTC, Allie Miller
Details


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 or GitHub 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:
RESOLVED FIXED

Description Allie Miller 2013-01-30 12:29:51 UTC
Created attachment 3305 [details]
Output

Case #23141
Using VS 2010, Windows 7 Ultimate with SP1 and an Android project with a few layout axml files. When trying to open any of them, the error message in the summary title appears with nothing showing in the source tab or just the XML shown.

Attached is one of the axml files. 

Have attempted
1) A replacement dll (provided by Xamarin) and copying it to C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Xamarin\Mono for Android\4.4.54. And making a copy of the old one.
2) Starting a new instance of Visual Studio, attaching the devenv.exe under processes and copied output.

The output is attached to this bug file
Comment 2 Lluis Sanchez 2013-01-31 11:27:54 UTC
Already fixed.