Downloads:
4,913
Downloads of v 0.0.4:
2,609
Last Update:
20 Sep 2020
Package Maintainer(s):
Software Author(s):
- Bill Curran
Tags:
bcurran3 unofficial choco toast notifications extensionChocolatey Toast Notifications Extension
- 1
- 2
- 3
0.0.4 | Updated: 20 Sep 2020
Downloads:
4,913
Downloads of v 0.0.4:
2,609
Maintainer(s):
Software Author(s):
- Bill Curran
Chocolatey Toast Notifications Extension 0.0.4
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Bill Curran. The inclusion of Bill Curran trademark(s), if any, upon this webpage is solely to identify Bill Curran goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Are Exempted or Have Failed
Not All Tests Have Passed
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Chocolatey Toast Notifications Extension, run the following command from the command line or from PowerShell:
To upgrade Chocolatey Toast Notifications Extension, run the following command from the command line or from PowerShell:
To uninstall Chocolatey Toast Notifications Extension, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download chocolatey-toast-notifications.extension --internalize --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade chocolatey-toast-notifications.extension -y --source="'INTERNAL REPO URL'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade chocolatey-toast-notifications.extension -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install chocolatey-toast-notifications.extension
win_chocolatey:
name: chocolatey-toast-notifications.extension
version: '0.0.4'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'chocolatey-toast-notifications.extension' do
action :install
source 'INTERNAL REPO URL'
version '0.0.4'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller chocolatey-toast-notifications.extension
{
Name = "chocolatey-toast-notifications.extension"
Version = "0.0.4"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'chocolatey-toast-notifications.extension':
ensure => '0.0.4',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator flcdrg on 21 Sep 2020.
choco://chocolatey-toast-notifications.extension
To use choco:// protocol URLs, install (unofficial) choco:// Protocol support
It's HERE! The 100% Chocolatey user OPT-IN toast notification extension for Chocolatey and Windows 10 (only).
Chocolatey Toast Notifications Extension is a Chocolatey extension that displays a toast notification after installing or uninstalling a program. This extension will start working automatically once installed and does NOT need to be implemented by package creators/maintainers. Chocolatey Toast Notifications Extension is meant to be installed and used directly by Chocolatey end users.
PURPOSE:
- Chocogeeky fun!
FEATURES:
- Chocolatey Toast Notifications Extension will display a toast notification with the package name, program name, program version, status message (installed or uninstalled), and a link to the package page on the chocolatey.org website after a program is installed or uninstalled.
WHAT IT WON'T DO:
- Chocolatey Toast Notifications Extension will NOT work on anything other than Windows 10, this is a limitation of the BurntToast PowerShell module and its use of the UWP Community Toolkit. (Yes, I tried it on Windows Server 2016 and it did NOT work.)
- Chocolatey Toast Notifications Extension will NOT display messages for programs that don't use standard installers, i.e. portable programs.
Click here to Patreon-ize the package maintainer.
# chocolatey-toast-notifications.extension v0.0.4 by Bill Curran AKA BCURRAN3 - 2018-2020 Copyleft Bill Curran
$scriptRoot = Split-Path -Path $MyInvocation.MyCommand.Definition
if (!(Test-Path "$ChocolateyInstall\extensions\chocolatey-toast-notifications\choco.ico")){
[System.Reflection.Assembly]::LoadWithPartialName('System.Drawing') | Out-Null
[System.Drawing.Icon]::ExtractAssociatedIcon("$env:ChocolateyInstall\choco.exe").ToBitmap().Save("$env:ChocolateyInstall\extensions\chocolatey-toast-notifications\choco.ico")
}
$publicFunctions = @(
'Get-ChocolateySoftwareName',
'Install-ChocolateyInstallPackageWithToastNotification',
'Uninstall-ChocolateyPackageWithToastNotification'
)
Get-ChildItem -Path "$scriptRoot\*.ps1" | ForEach-Object { . $_ }
Export-ModuleMember -Function $publicFunctions
Set-Alias Install-ChocolateyInstallPackage Install-ChocolateyInstallPackageWithToastNotification -Force -Scope Global
Set-Alias Uninstall-ChocolateyPackage Uninstall-ChocolateyPackageWithToastNotification -Force -Scope Global
# chocolatey-toast-notifications.extension v0.0.4 by Bill Curran AKA BCURRAN3 - 2018-2020 Copyleft Bill Curran
# This function gets the name (title) of the software being installed from the package .nuspec file.
# Morphed and expanded into Get-NuspecInfo.ps1 found in chocolatey-fastanswers.extension v0.0.2+
function Get-ChocolateySoftwareName{
$nuspecXML = "$env:ChocolateyInstall\lib\$env:chocolateyPackageName\$env:chocolateyPackageName.nuspec"
# Import title/softwareName
[xml]$nuspecFile = Get-Content $nuspecXML
$chocolateySoftwareName = $nuspecFile.package.metadata.title
return $chocolateySoftwareName
}
# chocolatey-toast-notifications.extension v0.0.4 by Bill Curran AKA BCURRAN3 - 2018-2020 Copyleft Bill Curran
# This function is aliased as Uninstall-ChocolateyPackage to intercept and run before
# Uninstall-ChocolateyPackage solely to add a a toast notification after running Uninstall-ChocolateyPackage.
# Got it? No? Read it again.
function Uninstall-ChocolateyPackageWithToastNotification{
# support for chocolatey-preinstaller-checks.extension
if (Get-Command Start-PreuninstallChecks -ErrorAction SilentlyContinue){Start-PreUninstallChecks}
# Remove temporary alias and resume normal operations
Remove-Item alias:\Uninstall-ChocolateyPackage -ErrorAction SilentlyContinue
# Execute Uninstall-ChocolateyInstallPackage actual
Uninstall-ChocolateyPackage @args
# Get name of program being uninstalled from the .nuspec
$chocolateySoftwareName = Get-ChocolateySoftwareName
# Check if WinRM is running (required to send Toast machine-wide)
$WinRMStatus=(Get-Service 'WinRM').Status
# Start WinRM if not Running
if ((Get-Service WinRM).Status -eq 'Stopped') {Start-Service 'WinRM' -ErrorAction SilentlyContinue}
# Show toast notification
if ((Get-Service WinRM).Status -eq 'Running') {
Invoke-Command -ComputerName $env:COMPUTERNAME -ArgumentList $env:chocolateyPackageName,$chocolateySoftwareName,$env:chocolateyPackageVersion -ScriptBlock {param([string]$chocolateyPackageName, [string]$chocolateySoftwareName, [string]$chocolateyPackageVersion) New-BurntToastNotification -Text "Chocolatey ($chocolateyPackageName)", "$chocolateySoftwareName v$chocolateyPackageVersion", "Uninstalled." -Button (New-BTButton -Content 'Package Webpage' -Arguments "https://chocolatey.org/packages/$env:chocolateyPackageName") -AppLogo "$env:ChocolateyInstall\extensions\chocolatey-toast-notifications\choco.ico"}
} else {
Write-Host "** Can't send global Toast because WinRM service is not running." -Foreground Red
}
# Stop WinRM if it was previously in Stopped state
if ($WinRMStatus -eq 'Stopped') {Stop-Service 'WinRM'}
}
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Chocolatey Toast Notifications Extension 0.0.4 | 2609 | Sunday, September 20, 2020 | Approved | |
Chocolatey Toast Notifications Extension 0.0.4-pre | 144 | Thursday, September 17, 2020 | Exempted | |
Chocolatey Toast Notifications Extension 0.0.3.1 | 364 | Tuesday, August 25, 2020 | Exempted | |
Chocolatey Toast Notifications Extension 0.0.3 | 1268 | Friday, December 14, 2018 | Exempted | |
Chocolatey Toast Notifications Extension 0.0.2 | 261 | Friday, November 23, 2018 | Exempted | |
Chocolatey Toast Notifications Extension 0.0.1 | 267 | Monday, September 3, 2018 | Exempted |
Copyleft Bill Curran
CHANGE LOG:
- 0.0.4 - Toasts now broadcast to all logged in users. Fixes problem when run with different credentials than the logged in user.
- 0.0.3.1 - Bug fix for background tasks sending foreground notifications
- 0.0.3 - Notifications will now display in the foreground when sent from a background task using the system account.
- 0.0.2 - baked in compatibility with chocolatey-preinstaller-checks.extension if installed, added win10 dependency
- 0.0.1 - initial release
ROADMAP:
- Possibly make it Windows 8 compatible after packaging up an old version of BurntToast
- Possibly make it Windows Server 2016 compatible.
-
- burnttoast-psmodule (≥ 0.6.2)
- dependency-windows10 (≥ 10.0)
Ground Rules:
- This discussion is only about Chocolatey Toast Notifications Extension and the Chocolatey Toast Notifications Extension package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Chocolatey Toast Notifications Extension, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.