David Gardiner
David Gardiner
Did a bit of research on this. It turns out that according to MSDN "[A small set of applications are pinned by default for new installations. Other than these, only...
Confirming that works. Here's a tidied up version (with `Close()` method calls) ```powershell Param($Target) $ValueData = ( Get-ItemProperty("HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\CommandStore\shell\Windows.taskbarpin") ).ExplorerCommandHandler $classesStarKey = (Get-Item "HKCU:\SOFTWARE\Classes").OpenSubKey("*", $true) $shellKey = $classesStarKey.CreateSubKey("shell", $true) $specialKey =...
@DavidNgoDev which thing in particular are you referring to as not working?
[`Install-ChocolateyShortcut`](https://chocolatey.org/docs/helpers-install-chocolatey-shortcut) is a Chocolatey function. I don't believe you can call those by default from a Boxstarter script. This issue is about `Install-ChocolateyPinnedTaskBarItem`
@teknowledgist That script talks about pinning to the start menu - does it pin to the task bar though?
Probably need to review them and figure out which ones are actionable and which ones may not be relevant.
They were just the default values created by the GitHub templates, but yeah that sounds like a better idea
But unfortunately GitHub Actions don't support that - https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#schedule I will tweak the schedules though
Feel free to create a PR. You'll need to update the chocolateyInstall.ps1 file and the nuspec file (to document the parameter) Also, if this also applies to the PDFXchangeEditor package,...