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

Host should inform user about different archs when failing to find framework #51102

Closed
vitek-karas opened this issue Apr 12, 2021 · 3 comments · Fixed by #107156
Closed

Host should inform user about different archs when failing to find framework #51102

vitek-karas opened this issue Apr 12, 2021 · 3 comments · Fixed by #107156
Labels
area-Host in-pr There is an active PR which will close this issue when it is merged
Milestone

Comments

@vitek-karas
Copy link
Member

Some systems support more than one architecture - for example Windows x86 and x64 on the same machine.
If I install:

  • .NET 5 x64
  • .NET 3.1 x86

And then I try to run dotnet my31app.dll it will fail to find a framework. This is because the default dotnet on the machine is the x64 one (installed first). The error message doesn't list/mention that there's a x86 one available.

Consider either informing the user of the existence of other architectures on the system, or potentially listing those in the output as well.

Related to #51101.

@ghost
Copy link

ghost commented Apr 12, 2021

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

Issue Details

Some systems support more than one architecture - for example Windows x86 and x64 on the same machine.
If I install:

  • .NET 5 x64
  • .NET 3.1 x86

And then I try to run dotnet my31app.dll it will fail to find a framework. This is because the default dotnet on the machine is the x64 one (installed first). The error message doesn't list/mention that there's a x86 one available.

Consider either informing the user of the existence of other architectures on the system, or potentially listing those in the output as well.

Related to #51101.

Author: vitek-karas
Assignees: -
Labels:

area-Host

Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 12, 2021
@vitek-karas
Copy link
Member Author

Similar problem applies if DOTNET_ROOT is not set correctly (for example it points to 32bit location) - it will also either fail to load completely or fail to resolve a framework. See #3745 for more details on that.

@vitek-karas
Copy link
Member Author

/cc @richlander

@vitek-karas vitek-karas removed the untriaged New issue has not been triaged by the area owner label Jul 9, 2021
@vitek-karas vitek-karas added this to the 6.0.0 milestone Jul 9, 2021
@agocke agocke modified the milestones: 6.0.0, 7.0.0 Aug 9, 2021
@agocke agocke added this to AppModel Jul 13, 2022
@agocke agocke modified the milestones: 7.0.0, 8.0.0 Jul 14, 2022
@agocke agocke modified the milestones: 8.0.0, Future Jul 26, 2023
@dotnet-policy-service dotnet-policy-service bot added the in-pr There is an active PR which will close this issue when it is merged label Aug 29, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Host in-pr There is an active PR which will close this issue when it is merged
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants