net development and WPF both in my day job and at home. I need to test this but turning that off isn't really practical for me.Naturally I wanted to use Visual Studio, as it’s the IDE I use all the time for.
![xamarin visual studio 2015 intellisense xamarin visual studio 2015 intellisense](https://www.windowsmode.com/wp-content/uploads/2017/02/Visual-Studio-2015-Debug.png)
#XAMARIN VISUAL STUDIO 2015 INTELLISENSE MAC#
I read somewhere that the file sharing between Mac and Windows might have something to do with this. I am also running using Parallels and Win8.1 (given up on W10). Obviously very busy because it never comes back. The above is all quite irritating but not nearly as bad as the fact the VS 2015 continues to regularly hang all the time, with a pop-up message saying Visual Studio Busy.
![xamarin visual studio 2015 intellisense xamarin visual studio 2015 intellisense](https://www.devsense.com/themes/devsense/img/phpvs2013.png)
Make sure you try this will stuff referenced in Xaml files as well as view model code. Best way to replicate this is to create a new solution and add a second PCL with some stuff in it and then refence that from your main project PCL. And also note that I think it only happens if I edit a Xaml file that is also referencing anything from my Core PCL, but I can't confirm this.
#XAMARIN VISUAL STUDIO 2015 INTELLISENSE CODE#
Note the errors are for any code that is referencing something in another PCL (my core PCL in my case). It all seems fine until the momemt I edit a Xaml file (thought it was fixed until this point) and then when I switch to a code file the errors all appear again. However, the other issue of intellisense errors appearing in code (which are not really errors) is not fixed. I have R# installed to so I dunno how weill intellisense works with out this but for me it seems good now. User80438 Xamarin.Forms 1.5.0-pre1 prerelease seems to fix the Blue underlining issues in the Xaml. You can either attach the test case back on a new comment in this thread, email it to the VS team as mentioned earlier, submit it in a bug report (optionally marked private), or send it to the support team via email (and ideally also mention my name in the email). That said, if anyone would like to submit a test case and a set of steps that they know consistently demonstrates the problem, that would be perfect too. It sounds like it is easy to reproduce even in a template app, so hopefully I will be able to see it quickly when I start experimenting. I haven't yet had a chance to try to reproduce the hanging behavior myself. (Really all the Xamarin.Forms Intellisense files are doing is feeding metadata to the built-in WPF XAML Intellisense engine.) One initial suspicion is that this hanging behavior might be within VS 2015 itself.
![xamarin visual studio 2015 intellisense xamarin visual studio 2015 intellisense](http://5kpcsoft.com/wp-content/uploads/2016/09/MICROSOFT-VISUAL-STUDIO-2015-ENTERPRISE-free-downlaod.jpg)
Unfortunately it sounds like the new Xamarin.Forms XAML Intellisense is still somehow leading to VS 2015 hangs. I believe both of the fixes in the Xamarin.Forms NuGet package are now included in the new Xamarin.Forms 1.5.0-pre1 prerelease. You can file that stack trace in a bug report, email it to the VS team (as mentioned by Daniel later in the thread), or if needed simply attach it to a comment at the end of this forum thread. If anyone would like, you can try collecting a stack trace from the frozen instance of VS, for example using the steps here. Reports of freezes related to this workaround are under investigation. It only affects VS 2015.) Workaround: (discussed at the top of this thread). (This is a bug in Xamarin.Forms caused by a change in the "ownership" of Intellisense from the XamarinVS extensions into the Xamarin.Forms NuGet package. Intellisense in VS 2015 does not work within XAML pages themselves, as discussed in the first comment on. in packages\Xamarin.Forms.1.4.4.*\build\portable*\ Possible workarounds: Downgrade to Xamarin.Forms 1.4.3.x (or earlier), or try changing: It affects all versions of Visual Studio.). You must add a reference to assembly ', Version=4.0.0.0"īug 32341 - Intellisense on code behind files for XAML pages is not available for InitializeComponent() or for elements of the XAML page that include the x:Name attribute. "The type 'Expression' is defined in an assembly that is not referenced.You must add a reference to assembly 'System.Runtime, Version=4.0.0.0" "The type 'Object' is defined in an assembly that is not referenced.The tentative plan is to ship the fix in Cycle 5 – Service Release 4 later this month, after Service Release 3 has been promoted to Stable.) Workaround: see Comment 4 on the bug report. (This one is a bug in the XamarinVS extensions themselves. Bug 32622 - Intellisense shows errors in VS 2015 when referencing certain types in app projects from PCL projects (due to the new Roslyn-based Intellisense in VS 2015).