Skip to content

Conversation

@aishwaryabh
Copy link
Contributor

@aishwaryabh aishwaryabh commented Aug 1, 2025

Issue describing the changes in this PR

resolves #2884

This image shows the previous behavior if we installed core tools through npm via running npm install -g azure-functions-core-tools@4 and running dotnet run after

image

Now we run the target with either bash or cmd depending on the target machine and now get the following output (tested with a local nuget package on my machine after running npm install -g azure-functions-core-tools@4)
image

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

@liliankasem
Copy link
Member

lgtm, but mind sharing another pkg for me to test? Can approve after I validate osx again.

Copy link
Member

@liliankasem liliankasem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

validated osx - lgtm

@aishwaryabh aishwaryabh merged commit 2efafa8 into main Aug 8, 2025
28 checks passed
@aishwaryabh aishwaryabh deleted the aibhandari/fix-func branch August 8, 2025 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dotnet run does not work on Windows when Core Tools are installed from NPM

3 participants