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

[NETE2ESDK] The parameter architecture and requesting should not be case sensitive in the Find Path feature. #1992

Open
NicoleWang001 opened this issue Oct 16, 2024 · 8 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed new-hire-issue P4

Comments

@NicoleWang001
Copy link
Member

Describe the bug.
If the value of parameter architecture and requesting contains uppercase letters, discovering .NET path is failed

Please attach log file(s) here if you have any.
The log file location should be copied to your clipboard if you came from VS Code.

Reproduction Steps
1.Download X64 SDK from https://dotnet.microsoft.com/en-us/download/dotnet and install.
2.Open VS Code and Run the 'Sample: Find the.NET on the PATH' command.
3. Enter the value of parameter architecture and requesting contains uppercase letters, eg. 'X64', or 'Greater_than_or_equal'
4.observe

Expected Behavior
.NET installation path should be found correctly

Exceptions & Errors (if any)
It returns non .NET installation path is found.
Image

.NET Install Tool Version
Preview 2.2.1

Your operating system? Please provide more detail, such as the version and or distro above.
N/A

VS Code Version
1.94.2

@nagilson
Copy link
Member

This is a good point, though this api will only be called by other code which will user lowercase version, so I would take this as a good first issue or open source thing to just lowercase the architecture string passed in here to the API.

@nagilson nagilson added help wanted Extra attention is needed good first issue Good for newcomers P4 new-hire-issue labels Oct 16, 2024
@nagilson
Copy link
Member

@NicoleWang001 Going forward, please don't include this issue in the table of issues. I think this is a good thing to raise and for us to fix, but it is low priority for the reasons above. I don't think we will fix it until there is someone we want to onboard to the repo or there is an open source person who wants to do it.

@agarwalishita
Copy link
Contributor

I can pick up this bug

@nagilson
Copy link
Member

Thank you @agarwalishita 😄 Ill be happy to review your PR if so

@agarwalishita
Copy link
Contributor

Image

Unable to find .net runtime architecture command here. Is there specific extension required for this command?

@nagilson
Copy link
Member

nagilson commented Nov 4, 2024

You will need to run the Sample extension to run the find path command as shown in the issue 😉

To do that you will need to build and then open the debug tab. Then in the debug tab you can select the sample extension drop down. Or, you can pack the sample extension as a .vsix file using vsce and then run the runtime extension to debug the code. There are some details about this in the readme of the repo.

The code in question is here, btw:

const arch = await vscode.window.showInputBox({

@v-xiaofchen
Copy link

This issue does not repro on 2.2.3.
Image

@agarwalishita
Copy link
Contributor

@nagilson you can close this issue as #2009 PR is merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed new-hire-issue P4
Projects
None yet
Development

No branches or pull requests

4 participants