-
Notifications
You must be signed in to change notification settings - Fork 64
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
Script does not read "RequirementsTemplateAppName" from preferences #1
Comments
This has been fixed. Thank you for the feedback 😄 |
Thanks! This script is great. Thank you for sharing it. I'll contribute what I can as I get it working in my environment. |
asjimene
pushed a commit
that referenced
this issue
Feb 5, 2020
Merge pull request #27 from ianperrin/master
asjimene
pushed a commit
that referenced
this issue
Jul 7, 2022
add options for alternate perference and recipe path
Clayo84
pushed a commit
to Clayo84/CMPackager
that referenced
this issue
Jun 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The script will throw errors messages when trying to apply rules to an application if you use any name other than "Application Requirements Template". The issues is due to the script not importing the name of the "RequirementsTemplateAppName". It currently uses a hard coded string.
The auto generated template is called "Application Requirements Template 1" causing rules to fail for most users.
Line 37 needs to be changed to:
$Global:RequirementsTemplateAppName = $PackagerPrefs.PackagerPrefs.RequirementsTemplateAppName
The text was updated successfully, but these errors were encountered: