Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IntelliSense is broken for the Xamarin.Android template (Type provider problem) #10837

Closed
Happypig375 opened this issue Jan 5, 2021 · 13 comments
Closed

IntelliSense is broken for the Xamarin.Android template (Type provider problem) #10837

Happypig375 opened this issue Jan 5, 2021 · 13 comments
Labels
Area-TypeProviders Bug Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.

Comments

@Happypig375
Copy link
Member

IntelliSense is broken for the Xamarin.Android template.

Repro steps

Provide the steps required to reproduce the problem:

  1. In Visual Studio 2019 (16.8.3), create a new project from the "Blank App (Android) F#" template.
  2. Open MainActivity.fs
  3. Under override this.OnCreate (bundle) =, press Control+Space.
  4. Observe that IntelliSense appears as normal.
  5. Build the project once.
  6. Observe that IntelliSense is broken.
  7. Hover over Resource in type Resources = <Project name>.Resource.
  8. Observe an error related to type providers.

image
image

If possible attach a zip file with the repro case. This often makes it easier for others to reproduce.
The zip file should ideally represent the situation just before the call/step that is problematic.

AndroidIntellisense.zip

Expected behavior

IntelliSense should work just like before building the project.

Actual behavior

IntelliSense is broken and unusable.

Known workarounds

IntelliSense still works after dots, provided that <Project name>.Resource is not included in the resulting list.

Related information 
Microsoft Visual Studio Community 2019
Version 16.8.3
VisualStudio.16.Release/16.8.3+30804.86
Microsoft .NET Framework
Version 4.8.04084

Installed Version: Community

Visual C++ 2019   00435-60000-00000-AA759
Microsoft Visual C++ 2019

ADL Tools Service Provider   1.0
This package contains services used by Data Lake tools

ASA Service Provider   1.0

ASP.NET and Web Tools 2019   16.8.554.20160
ASP.NET and Web Tools 2019

ASP.NET Core Razor Language Services   16.1.0.2052803+84e121f1403378489b842e1797df2f3f5a49ac3c
Provides languages services for ASP.NET Core Razor.

ASP.NET Web Frameworks and Tools 2019   16.8.554.20160
For additional information, visit https://www.asp.net/

Azure App Service Tools v3.0.0   16.8.554.20160
Azure App Service Tools v3.0.0

Azure Data Lake Node   1.0
This package contains the Data Lake integration nodes for Server Explorer.

Azure Data Lake Tools for Visual Studio   2.6.3000.0
Microsoft Azure Data Lake Tools for Visual Studio

Azure Stream Analytics Tools for Visual Studio   2.6.3000.0
Microsoft Azure Stream Analytics Tools for Visual Studio

C# Tools   3.8.0-5.20604.10+9ed4b774d20940880de8df1ca8b07508aa01c8cd
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.

Dotfuscator Community Edition   5.42.0.9514-e0e25f754
PreEmptive Protection - Dotfuscator CE

Extensibility Message Bus   1.2.6 (master@34d6af2)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.

IntelliCode Extension   1.0
IntelliCode Visual Studio Extension Detailed Info

Microsoft Azure HDInsight Azure Node   2.6.3000.0
HDInsight Node under Azure Node

Microsoft Azure Hive Query Language Service   2.6.3000.0
Language service for Hive query

Microsoft Azure Stream Analytics Language Service   2.6.3000.0
Language service for Azure Stream Analytics

Microsoft Azure Stream Analytics Node   1.0
Azure Stream Analytics Node under Azure Node

Microsoft Azure Tools   2.9
Microsoft Azure Tools for Microsoft Visual Studio 2019 - v2.9.30924.1

Microsoft Continuous Delivery Tools for Visual Studio   0.4
Simplifying the configuration of Azure DevOps pipelines from within the Visual Studio IDE.

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Microsoft Library Manager   2.1.113+g422d40002e.RR
Install client-side libraries easily to any web project

Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers

Microsoft Visual C++ Wizards   1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio Tools for Containers   1.1
Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.

Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package

Mono Debugging for Visual Studio   16.8.43 (00471f8)
Support for debugging Mono processes with Visual Studio.

Node.js Tools   1.5.20902.1 Commit Hash:b474efcb6f92db52a8f8e2e6a8cb9648476885cc
Adds support for developing and debugging Node.js apps in Visual Studio

NuGet Package Manager   5.8.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

ProjectServicesPackage Extension   1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

SQL Server Data Tools   16.0.62010.06180
Microsoft SQL Server Data Tools

ToolWindowHostedEditor   1.0
Hosting json editor into a tool window

TypeScript Tools   16.0.21016.2001
TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools   3.8.0-5.20604.10+9ed4b774d20940880de8df1ca8b07508aa01c8cd
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools   16.8.0-beta.20507.4+da6be68280c89131cdba2045525b80890401defd
Microsoft Visual F# Tools

Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Container Tools Extensions   1.0
View, manage, and diagnose containers within Visual Studio.

Visual Studio Tools for Containers   1.0
Visual Studio Tools for Containers

Visual Studio Tools for Unity   4.8.2.0
Visual Studio Tools for Unity

VisualStudio.DeviceLog   1.0
Information about my package

VisualStudio.Foo   1.0
Information about my package

VisualStudio.Mac   1.0
Mac Extension for Visual Studio

Xamarin   16.8.000.260 (d16-8@fd405a2)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Designer   16.8.0.507 (remotes/origin/d16-8@e87b24884)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

Xamarin Templates   16.8.112 (86385a3)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

Xamarin.Android SDK   11.1.0.17 (d16-8/c0e2b8e)
Xamarin.Android Reference Assemblies and MSBuild support.
    Mono: be2226b
    Java.Interop: xamarin/java.interop/d16-8@79d9533
    ProGuard: Guardsquare/proguard/proguard6.2.2@ebe9000
    SQLite: xamarin/sqlite/3.32.1@1a3276b
    Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-8@2fb1cbc


Xamarin.iOS and Xamarin.Mac SDK   14.6.0.15 (87a1b18d8)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
@cartermp
Copy link
Contributor

cartermp commented Jan 5, 2021

labeling external for now since the template isn't owned in this repository.

@Happypig375
Copy link
Member Author

@cartermp One type breaking the entire IntelliSense is undesirable and certainly should be fixed.

@Happypig375
Copy link
Member Author

@cartermp How can this be resolved? Where are the templates owned?

@cartermp
Copy link
Contributor

cartermp commented Feb 6, 2021

I don't know. I would start here though: xamarin/Xamarin.Android.FSharp.ResourceProvider#9

It appears the type provider has further issues and so merely finding the right things and updating them won't fix things.

@Happypig375
Copy link
Member Author

@cartermp But surely the F# IntelliSense can be modified such that one faulty type provider will not ruin the whole IntelliSense suggestions list? Maybe just that faulty type can have an accompanying error icon, but other classes should still be shown.

@cartermp
Copy link
Contributor

cartermp commented Feb 7, 2021

Maybe, but type providers are "special" in several ways. @dsyme could dive into more

@KevinRansom KevinRansom added Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code. Bug labels Jul 21, 2021
@nbevans
Copy link

nbevans commented Oct 19, 2021

Impact low?

@nbevans
Copy link

nbevans commented Oct 19, 2021 •
edited
Loading

dotnet/android#6404
xamarin/Xamarin.Android.FSharp.ResourceProvider#9

It is all interlinked ^ and Android F# app builds are broken as of right now. Looks like been this way for months actually.

@Happypig375 Happypig375 mentioned this issue Jan 25, 2022
Closed
@TimLariviere TimLariviere mentioned this issue Jan 31, 2022
Closed
@TimLariviere
Copy link

Created a replacement for Xamarin.Android.FSharp.ResourceProvider. IntelliSense works again after compiling one time and reloading the project/solution.
https://github.com/fabulousfx/FSharp.Android.Resource

@dsyme
Copy link
Contributor

dsyme commented Mar 31, 2022

I'm going to close this as our recommendation is to use the replacement above

@dsyme dsyme closed this as completed Mar 31, 2022
@knocte
Copy link

knocte commented Mar 31, 2022

I'm going to close this as our recommendation is to use the replacement above

Hey Don, if this is a solution blessed by MS, shouldn't it live in a different org? I mean, it is now in "fabulousfx", which is hard to find, and would make people think is only for the Fabulous framework.

@dsyme
Copy link
Contributor

dsyme commented Apr 4, 2022

@TimLariviere Should we move fsprojects/Fabulous into fabulousfx?

@TimLariviere
Copy link

@dsyme Yes, this would be great. I'm planning to extract non-"core" stuff into other repositories, so having everything in a separate org would be a good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-TypeProviders Bug Impact-Low (Internal MS Team use only) Describes an issue with limited impact on existing code.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@knocte @nbevans @KevinRansom @cartermp @TimLariviere @dsyme @Happypig375