-
Notifications
You must be signed in to change notification settings - Fork 24
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
Multiple issues / feature requests #2
Comments
Glad you're digging it!
Not really sure why this is the case but seems like it's a bug.
Interesting. I haven't actually done this in a while so maybe it broke with Win11.
Just fixed this. |
Thank you for the fast reply! I also think it might be a misunderstanding on my part with where to "nest" the New-InstallerDirectory items and New-InstallerShortcut within the New-Installer -Content script block. I may have things in the wrong place? Here's an example... `[CmdletBinding()] Import-Module psmsi New-Installer -ProductName $ProductName -Manufacturer $Publisher -UpgradeCode $UpgradeCode -Content { |
Overall - I (LOVE) this module and it does make a solid installer package. Thank you!
Maybe it's just my ignorance, but the -Platform option doesn't have any effect on the target path when I use ProgramFilesFolder. It always installs to \Program Files (x86). Is there a way to install to \Program Files or even a custom location?
On Windows 11, the -NewInstallerShortcut doesn't seem to have any effect after installation. No shortcut appears on Start, Taskbar or Desktop. Maybe I'm misunderstanding that?
The documentation markdown shows -Product, but the function expects -ProductId or -ProductName (ambiguous).
The text was updated successfully, but these errors were encountered: