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

Cannot Launch Performance Profiler with Uno 5.4 Project and Visual Studio 2022 #18626

Open
brswan opened this issue Oct 30, 2024 · 1 comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification

Comments

@brswan
Copy link

brswan commented Oct 30, 2024

Current behavior

I am trying to perform a memory profile on a newly create Uno app. I created a new Uno 5.4 Desktop app. I am running in Windows.

Whenever I try to launch from the Performance Profiler I get the following error:
AppName failed to launch. Unable to obtain package full name from target

Expected behavior

Performance Profiler starts when app launches.

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

Create a new Uno App using Template.
Target an Uno Desktop app.
In Visual Studio 2022 select Debug > Performance Profiler
Check the Memory Usage check box
Select Start

Workaround

None at this time

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

image

Affected platforms

Skia (WPF)

IDE

Visual Studio 2022

IDE version

17.11.5

Relevant plugins

No response

Anything else we need to know?

No response

@brswan brswan added difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification labels Oct 30, 2024
@jeromelaban
Copy link
Member

Thanks for the report. This indeed looks like a bug in visual studio, where the profiler does not know what to choose from.

As a workaround you can temporarily remove all the targetframeworks but the net8.0-desktop one, reload the project, then launch the profiler. We can track the issue in Visual Studio's Developer Community.

Looking further down, it seems that this behavior happens when any of the ios, android or macatalyst targets are present in TargetFrameworks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty/tbd Categorizes an issue for which the difficulty level needs to be defined. kind/bug Something isn't working triage/untriaged Indicates an issue requires triaging or verification
Projects
None yet
Development

No branches or pull requests

2 participants