@RickStrahl see my comment in the issue :-)
# Script builds a Chocolatey Package and tests it locally
#
# Assumes: Uses latest release out of Pre-release folder
# Release has been checked in to GitHub Repo
# Builds: ChocolateyInstall.ps1 file with download URL and sha256 embedded
cd "$PSScriptRoot"
remove-item ".\tools" -recurse -force
# $sourceFolder = "..\Distribution"
# $file = "$sourceFolder\MarkdownMonster.exe"
# write-host $file
# $sha = get-filehash -path "$file" -Algorithm SHA256 | select -ExpandProperty "Hash"
# write-host $sha
robocopy $sourceFolder .\tools /MIR
copy ..\license.txt .\tools\license.txt
#empty install file - we just have content no code
#$filetext = ""
#out-file -filepath .\tools\chocolateyinstall.ps1 -inputobject $filetext
# uninstall script
# copy chocolateyuninstall.ps1 .\tools
#$filetext = @"
#MarkdownMonster.exe
#Sha256: $sha
#"@
# out-file -filepath .\tools\verify.txt -inputobject $filetext
del *.nupkg
# Create .nupkg from .nuspec
choco pack
choco uninstall "MarkdownMonster.Portable"
choco install "MarkdownMonster.Portable" -fdv -y -s ".\"
Thanks for your help.
As a nice side effect I looked a lot closer at running the portable version and found a few more little things that weren't working right that got fixed (like missing icons) and a few other UI quiks.
:+1:
you know, if you wanted, you could embed the exe into this package as well: https://chocolatey.org/packages/MarkdownMonster rather than first downloading it as well, that would also save the need for the checksums :-D
It looks like it made it but choco push is totally hung.
I remember this happened with the previous version as well. Console is dead I have to shut it down.
eventually returned. It says it's timed out, but the package is up on choco.
any ideas Rob?
:point_up: January 15, 2017 3:34 AM
Yip, if it is an embedded package, with just contents, Chocolatey will wipe out the folder on uninstallation
Chocolatey is a tad bit smarter than that. On uninstall it removes all unchanged files and leaves files that have changed. If you uninstall with force, it will wipe all files, including files created and user changed files. Same goes for upgrade.
@RickStrahl @gep13 chocolatey/choco#1139 for the uninstall issue - it looks like something was running and locking the folder, so when it moves the files to lib-bkp and later attempts to delete them, it fails because the locked files are now there.
:point_up: January 15, 2017 4:26 AM for the push hang. I push up 7MB and don't run into this very often. Let me see if maintenance can clear this up.
@ferventcoder I did run from a local folder install for testing though - not sure if that would make a difference. I give it another try now after reboot.
This is a portable install and shouldn't need any admin rights to install. No admin tag in the nuspec.
@ferventcoder @gep13 Shouldn't I be able to install from a non-elevated prompt with this portable install?
The default installation directory is locked down to admins only with modify access
we highlight that in the more options section oh the install page. Also on the security page
@ferventcoder Ok, fair enough. I was under the impression that Chocolatey could run under limited rights, because that's what several people were asking for. So when I don't specify Admin rights on the installer does it run the installer under Admin as well or under user account? I thought this was the whole point of a portable, non-admin capable install.
We probably should move this over to @chocolate.org group :-)
In 1.1.20 of Markdown Monster. No more @Razor code block required to figure out the file name.
That feature needs a little more work - like it should also capture a title from FrontMatter.
will give that a try as well