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

[VS] Single project - quickly switching targets and F5 causes error #16516

Open
MartinZikmund opened this issue Apr 30, 2024 · 4 comments · May be fixed by #19454
Open

[VS] Single project - quickly switching targets and F5 causes error #16516

MartinZikmund opened this issue Apr 30, 2024 · 4 comments · May be fixed by #19454
Labels
blocked/vs Categorizes an issue as blocked by a Visual Studio problem kind/bug Something isn't working

Comments

@MartinZikmund
Copy link
Member

MartinZikmund commented Apr 30, 2024 •
edited
Loading

Current behavior

When I switch targets and F5 in quick succession, I get intermittent error in console:

1>Error: Cannot access a disposed object.
1>Object name: 'Microsoft.VisualStudio.ProjectSystem.ConfiguredProjectImpl'.

Second F5 works fine

Expected behavior

No error

How to reproduce it (as minimally and precisely as possible)

No response

Workaround

  • Run the debug again or
  • Wait a bit longer between the switches between targets

Works on UWP/WinUI

None

Environment

Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia

NuGet package version(s)

No response

Affected platforms

No response

IDE

Visual Studio 2022

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response
@MartinZikmund MartinZikmund added kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. blocked/vs Categorizes an issue as blocked by a Visual Studio problem and removed triage/untriaged Indicates an issue requires triaging or verification difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. labels Apr 30, 2024
@MartinZikmund
Copy link
Member Author

MartinZikmund commented Apr 30, 2024 •
edited
Loading

I guess this must be already tracked somewhere, if yes, feel free to close as dupe

@jeromelaban
Copy link
Member

This is caused by:

  1. net8.0 must be first for WSL debugging to work
  2. net8.0 must be first for WebAssembly publishing/debugging to work
  3. net8.0-windows10 needs to be first for WinAppSDK Hot reload to work

@ADD-David-Antolin
Copy link

@jeromelaban notice they (bot) closed you the second one as duplicated of the first one.

@Youssef1313 Youssef1313 mentioned this issue Apr 30, 2024
Open
@jeromelaban
Copy link
Member

@ADD-David-Antolin yes we noticed, and it's known on the Microsoft side, it will be adjusted.

@jeromelaban jeromelaban linked a pull request Feb 5, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked/vs Categorizes an issue as blocked by a Visual Studio problem kind/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(vs): Remove VS reload project on TFM for browserwasm target unoplatform/uno
3 participants
@MartinZikmund @jeromelaban @ADD-David-Antolin