Bug 38829 - Suspending ReSharper is not sufficient to re-enable Xamarin.Forms IntelliSense extension, and the extension does not emit any warning messages to indicate that it is disabled
Summary: Suspending ReSharper is not sufficient to re-enable Xamarin.Forms IntelliSens...
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: 15.3
Assignee: Adrian Alonso
Depends on:
Reported: 2016-02-17 04:00 UTC by Brendan Zagaeski (Xamarin Team, assistant)
Modified: 2017-06-16 19:44 UTC (History)
7 users (show)

Tags: NotRegression
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:

Description Brendan Zagaeski (Xamarin Team, assistant) 2016-02-17 04:00:44 UTC
Suspending ReSharper is not sufficient to re-enable Xamarin.Forms IntelliSense extension, and the extension does not emit any warning messages to indicate that it is disabled

This is an enhancement request to refine the behavior introduced by the fix for Bug 29721 that automatically disables the Xamarin.Forms.Intellisense extension when ReSharper is installed.

## Possible improvements

- Add extra logic in the Xamarin.Forms.Intellisense extension that detects the presence of ReSharper so that the extension can identify the case where ReSharper is installed but suspended and re-enable itself in that case.

- Add an obvious warning message in the log files that states something like "The Xamarin.Forms IntelliSense extension is disabling itself because ReSharper has been detected as being installed. If you have also suspended ReSharper, you will get NO IntelliSense in Xamarin.Forms XAML files." 

## Regression status: not applicable, feature request

Tested on: XamarinVS (dcea9c1)

## Steps followed to replicate

1. Install ReSharper 10.0.2 Trial into Visual Studio 2013 Update 5.

2. Open Visual Studio.

3. Navigate to "Tools -> Options -> ReSharper Ultimate".

4. Choose the "Suspend Now" button to temporarily disable ReSharper functionality.

5. Restart Visual Studio, just to be thorough.

6. Create a new "Visual C# -> Cross-Platform -> Blank App (Xamarin.Forms Portable)" project.

7. Right-click the PCL project and select "Add -> New Item -> Forms Xaml Page".

8. Open the XAML page in the editor window.

9. Type `<` to request auto-completion for a new element within the `<ContentPage>` element.

10. Optionally quit and restart Visual Studio, re-open the project, and repeat step 9 a couple times (to prove that Bug 34023 is not involved).

## Results

The Xamarin.Forms.Intellisense extension remains deactivated, so only the basic XML auto-completions are offered:

> <!--
> <![CDATA[
> <?
Comment 6 Adrian Alonso 2017-06-16 19:44:49 UTC
This is no longer valid because intellisense is provided by the Forms nuget packages now.