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

During discovery, traverse links #474

Open
SteveL-MSFT opened this issue Jun 21, 2024 · 1 comment
Open

During discovery, traverse links #474

SteveL-MSFT opened this issue Jun 21, 2024 · 1 comment
Assignees
Labels
Milestone

Comments

@SteveL-MSFT
Copy link
Member

Summary of the new feature / enhancement

Exe's published to the MSStore as msix packages have a link to the exe in PATH. However, if they are resources, then their resource manifests won't be found as they are not actually in PATH.

Proposed technical implementation details (optional)

When an exe which is a link is found, dsc should traverse the link to the home of the exe to find a resource manifest. Separately, some caching might make sense if this turns out to be too expensive.

@SteveL-MSFT SteveL-MSFT added Issue-Enhancement The issue is a feature or idea Needs Triage labels Jun 21, 2024
@SteveL-MSFT SteveL-MSFT added this to the Post-3.0 milestone Jun 21, 2024
@SteveL-MSFT SteveL-MSFT modified the milestones: Post-3.0, 3.0-RC Aug 6, 2024
@anmenaga
Copy link
Collaborator

Related issue #559 .

@SteveL-MSFT SteveL-MSFT modified the milestones: 3.0-RC, Post-3.0 Oct 2, 2024
@SteveL-MSFT SteveL-MSFT modified the milestones: Post-3.0, 3.1-Consider Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants