Bug 32953 - VS 2015 freezes after typing Grid.
Summary: VS 2015 freezes after typing Grid.
Status: RESOLVED DUPLICATE of bug 32909
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.5.0
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-08-11 07:22 UTC by Dominik Leeb
Modified: 2015-08-11 07:58 UTC (History)
4 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 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 DUPLICATE of bug 32909

Description Dominik Leeb 2015-08-11 07:22:49 UTC
Hello,

I installed Xamarin.Forms Version 1.5.0.6396-pre1 to get Intellisense for XAML working in VS 2015. Intellisense now works fine but as soon as i type '<Grid.' Visual Studio freezes. To make things clear, after writing the dot sign Visual Studio freezes.

OS is Windows 10. I noticed the same problem occurs when writing the dot after '<ContentView'. Also tried it with '<ListView.' and '<Label.' where it works like a charm.

PS: I know its a pre-release, just submitting the bug if you might not know about it yet.
Comment 1 Rajneesh Kumar 2015-08-11 07:58:37 UTC

*** This bug has been marked as a duplicate of bug 32909 ***