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

Workaround for $PSScriptRoot issue #574

Closed

Conversation

AndrewDemski-ad-gmail-com
Copy link
Contributor

Proposed Changes

Alternative script path handling which does not rely on $PSScriptRoot.
Expandable approach to deal with PS1 files which must be loaded into PowerShell at initial stage of execution.

might need exclusions of future "*.tests.ps1" files from Pester

Related Issues

[PR comment][autolink-references]

AndrewDemski-ad-gmail-com referenced this pull request Feb 24, 2024
@KnifMelti
I made few adjustments to allow mods to be put inside Intunewim package. This way, we can run install command with `%programdata%\Winget-AutoUpdate\Winget-Install.ps1` and it should copy mods from the intunewim to the WAU mod location
@Romanitho
Copy link
Owner

This may change if we start working on an MSI Installer I guess

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.

2 participants