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.

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

XAML Autocomplete and Previewer does not work #430

Open
alessandrofrancesconi opened this issue Dec 12, 2023 · 1 comment
Open

XAML Autocomplete and Previewer does not work #430

alessandrofrancesconi opened this issue Dec 12, 2023 · 1 comment
Labels

Comments

@alessandrofrancesconi
Copy link

alessandrofrancesconi commented Dec 12, 2023

Describe the bug

I'm working on a Avalonia 11 multiplatform project, for Android and iOS. Suddenly, the XAML editor does not provide autocompletion/IntelliSense anymore (CTRL+Space does not show anything), and the preview box is always empty:

image

The project compiles fine, tested with both .NET 7 and .NET 8.

Other projects I had using the same Avalonia version works. How can I collect the necessary information to have a comprehensive view of what's broken?

To Reproduce

I did not found a way to reproduce on another PC.

AvaloniaVS plugin version

11.5

Avalonia version

11.0.6

Visual Studio version

17.8.3

Relevant log output

Avalonia Diagnostics tab is empty

Additional context

No response

@jonasnordlund
Copy link

jonasnordlund commented Dec 15, 2023

I'm a new user of Avalonia + AvaloniaVS and same here. I first used Avalonia 11.0.6 as it was the latest release, then downgraded Avalonia to 11.0.4 as it was said this extension didn't yet support 11.0.6.

However, I still have this problem.

Update 1: Hmm, I get an Avalonia Diagnostics stack trace that makes it looks much like #183 for me. I do have a C++ project present in my solution as a reference for the code I'm in fact translating to Avalonia, and might try unloading it.

Update 2: Alright, that moved me ahead somewhat. Now I got hit by AvaloniaUI/Avalonia/discussions/13667
which was due to it being a NativeAOT project.

I think this extension lacking NativeAOT support and mixed code (C++) in the solution should be on the front page. It's starting to get disheartening and frustrating to discover these issues on my own when they are known issues affecting common project setups.

I'm not sure if this helped you, but I got here because these problems resulted in the very same issue as here. Leaving my findings as references to others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants