diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/ReadMe.md b/OrganizeIt.Cli/OrganizeIt.Cli/ReadMe.md deleted file mode 100644 index 3c09236..0000000 --- a/OrganizeIt.Cli/OrganizeIt.Cli/ReadMe.md +++ /dev/null @@ -1,133 +0,0 @@ -## Summary -How do I create packages? See https://docs.chocolatey.org/en-us/create/create-packages - -If you are submitting packages to the community feed (https://community.chocolatey.org) -always try to ensure you have read, understood and adhere to the create -packages wiki link above. - -## Automatic Packaging Updates? -Consider making this package an automatic package, for the best -maintainability over time. Read up at https://docs.chocolatey.org/en-us/create/automatic-packages - -## Shim Generation -Any executables you include in the package or download (but don't call -install against using the built-in functions) will be automatically shimmed. - -This means those executables will automatically be included on the path. -Shim generation runs whether the package is self-contained or uses automation -scripts. - -By default, these are considered console applications. - -If the application is a GUI, you should create an empty file next to the exe -named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'. -See https://docs.chocolatey.org/en-us/create/create-packages#how-do-i-set-up-shims-for-applications-that-have-a-gui - -If you want to ignore the executable, create an empty file next to the exe -named 'name.exe.ignore' e.g. 'bob.exe' would need a file named -'bob.exe.ignore'. -See https://docs.chocolatey.org/en-us/create/create-packages#how-do-i-exclude-executables-from-getting-shims - -## Self-Contained? -If you have a self-contained package, you can remove the automation scripts -entirely and just include the executables, they will automatically get shimmed, -which puts them on the path. Ensure you have the legal right to distribute -the application though. See https://docs.chocolatey.org/en-us/information/legal. - -You should read up on the Shim Generation section to familiarize yourself -on what to do with GUI applications and/or ignoring shims. - -## Automation Scripts -You have a powerful use of Chocolatey, as you are using PowerShell. So you -can do just about anything you need. Choco has some very handy built-in -functions that you can use, these are sometimes called the helpers. - -### Built-In Functions -https://docs.chocolatey.org/en-us/create/functions - -A note about a couple: -* Get-ToolsLocation - used to get you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder - see https://docs.chocolatey.org/en-us/create/functions/get-toolslocation -* Install-BinFile - used for non-exe files - executables are automatically shimmed... - see https://docs.chocolatey.org/en-us/create/functions/install-binfile -* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed - see https://docs.chocolatey.org/en-us/create/functions/uninstall-binfile - -### Getting package specific information -Use the package parameters pattern - see https://docs.chocolatey.org/en-us/guides/create/parse-packageparameters-argument - -### Need to mount an ISO? -https://docs.chocolatey.org/en-us/guides/create/mount-an-iso-in-chocolatey-package - -### Environment Variables -Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow): - - * TEMP/TMP - Overridden to the CacheLocation, but may be the same as the original TEMP folder - * ChocolateyInstall - Top level folder where Chocolatey is installed - * ChocolateyPackageName - The name of the package, equivalent to the `` field in the nuspec - * ChocolateyPackageTitle - The title of the package, equivalent to the `` field in the nuspec - * ChocolateyPackageVersion - The normalized version of the package, equivalent to a normalized edition of the `<version />` field in the nuspec - * ChocolateyPackageFolder - The top level location of the package folder - the folder where Chocolatey has downloaded and extracted the NuGet package, typically `C:\ProgramData\chocolatey\lib\packageName`. - -#### Advanced Environment Variables -The following are more advanced settings: - - * ChocolateyPackageParameters - Parameters to use with packaging, not the same as install arguments (which are passed directly to the native installer). Based on `--package-parameters`. - * CHOCOLATEY_VERSION - The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. Otherwise take a dependency on the specific version you need. - * ChocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. Automatically handled in built in Choco functions. - * OS_PLATFORM - Like Windows, macOS, Linux. - * OS_VERSION - The version of OS, like 10.0 something something for Windows. - * OS_NAME - The reported name of the OS. - * USER_NAME = The user name - * USER_DOMAIN = The user domain name (could also be local computer name) - * IS_PROCESSELEVATED = Is the process elevated? - * IS_SYSTEM = Is the user the system account? - * IS_REMOTEDESKTOP = Is the user in a terminal services session? - * ChocolateyToolsLocation - formerly 'ChocolateyBinRoot' ('ChocolateyBinRoot' will be removed with Chocolatey v2.0.0), this is where tools being installed outside of Chocolatey packaging will go. - -#### Set By Options and Configuration -Some environment variables are set based on options that are passed, configuration and/or features that are turned on: - - * ChocolateyEnvironmentDebug - Was `--debug` passed? If using the built-in PowerShell host, this is always true (but only logs debug messages to console if `--debug` was passed) - * ChocolateyEnvironmentVerbose - Was `--verbose` passed? If using the built-in PowerShell host, this is always true (but only logs verbose messages to console if `--verbose` was passed). - * ChocolateyExitOnRebootDetected - Are we exiting on a detected reboot? Set by ` --exit-when-reboot-detected` or the feature `exitOnRebootDetected` - * ChocolateyForce - Was `--force` passed? - * ChocolateyForceX86 - Was `-x86` passed? - * ChocolateyRequestTimeout - How long before a web request will time out. Set by config `webRequestTimeoutSeconds` - * ChocolateyResponseTimeout - How long to wait for a download to complete? Set by config `commandExecutionTimeoutSeconds` - * ChocolateyPowerShellHost - Are we using the built-in PowerShell host? Set by `--use-system-powershell` or the feature `powershellHost` - -#### Business Edition Variables - - * ChocolateyInstallArgumentsSensitive - Encrypted arguments passed from command line `--install-arguments-sensitive` that are not logged anywhere. - * ChocolateyPackageParametersSensitive - Package parameters passed from command line `--package-parameters-sensitive` that are not logged anywhere. - * ChocolateyLicensedVersion - What version is the licensed edition on? - * ChocolateyLicenseType - What edition / type of the licensed edition is installed? - * USER_CONTEXT - The original user context - different when self-service is used (Licensed) - -#### Experimental Environment Variables -The following are experimental or use not recommended: - - * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under - * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different - based on git describe - * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. - * IS_REMOTE = Is the user in a remote session? - -#### Not Useful Or Anti-Pattern If Used - - * ChocolateyInstallOverride = Not for use in package automation scripts. Based on `--override-arguments` being passed. - * ChocolateyInstallArguments = The installer arguments meant for the native installer. You should use chocolateyPackageParameters instead. Based on `--install-arguments` being passed. - * ChocolateyIgnoreChecksums - Was `--ignore-checksums` passed or the feature `checksumFiles` turned off? - * ChocolateyAllowEmptyChecksums - Was `--allow-empty-checksums` passed or the feature `allowEmptyChecksums` turned on? - * ChocolateyAllowEmptyChecksumsSecure - Was `--allow-empty-checksums-secure` passed or the feature `allowEmptyChecksumsSecure` turned on? - * ChocolateyChecksum32 - Was `--download-checksum` passed? - * ChocolateyChecksumType32 - Was `--download-checksum-type` passed? - * ChocolateyChecksum64 - Was `--download-checksum-x64` passed? - * ChocolateyChecksumType64 - Was `--download-checksum-type-x64` passed? - * ChocolateyPackageExitCode - The exit code of the script that just ran - usually set by `Set-PowerShellExitCode` - * ChocolateyLastPathUpdate - Set by Chocolatey as part of install, but not used for anything in particular in packaging. - * ChocolateyProxyLocation - The explicit proxy location as set in the configuration `proxy` - * ChocolateyDownloadCache - Use available download cache? Set by `--skip-download-cache`, `--use-download-cache`, or feature `downloadCache` - * ChocolateyProxyBypassList - Explicitly set locations to ignore in configuration `proxyBypassList` - * ChocolateyProxyBypassOnLocal - Should the proxy bypass on local connections? Set based on configuration `proxyBypassOnLocal` - * http_proxy - Set by original `http_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set. - * https_proxy - Set by original `https_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set. - * no_proxy- Set by original `no_proxy` passthrough, or same as `ChocolateyProxyBypassList` if explicitly set. - diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/_TODO.txt b/OrganizeIt.Cli/OrganizeIt.Cli/_TODO.txt deleted file mode 100644 index 50bca03..0000000 --- a/OrganizeIt.Cli/OrganizeIt.Cli/_TODO.txt +++ /dev/null @@ -1,131 +0,0 @@ -TODO - -1. Determine Package Use: - - Organization? Internal Use? - You are not subject to distribution - rights when you keep everything internal. Put the binaries directly - into the tools directory (as long as total nupkg size is under 1GB). - When bigger, look to use from a share or download binaries from an - internal location. Embedded binaries makes for the most reliable use - of Chocolatey. Use `$fileLocation` (`$file`/`$file64`) and - `Install-ChocolateyInstallPackage`/`Get-ChocolateyUnzip` in - tools\chocolateyInstall.ps1. - - You can also choose to download from internal urls, see the next - section, but ignore whether you have distribution rights or not, it - doesn't apply. Under no circumstances should download from the - internet, it is completely unreliable. See - https://docs.chocolatey.org/en-us/community-repository/community-packages-disclaimer - to understand the limitations of a publicly available repository. - - Community Repository? - Have Distribution Rights? - If you are the software vendor OR the software EXPLICITLY allows - redistribution and the total nupkg size will be under 200MB, you - have the option to embed the binaries directly into the package to - provide the most reliable install experience. Put the binaries - directly into the tools folder, use `$fileLocation` (`$file`/ - `$file64`) and `Install-ChocolateyInstallPackage`/ - `Get-ChocolateyUnzip` in tools\chocolateyInstall.ps1. Additionally, - fill out the LICENSE and VERIFICATION file (see 3 below and those - files for specifics). - - NOTE: You can choose to download binaries at runtime, but be sure - the download location will remain stable. See the next section. - - Do Not Have Distribution Rights? - - Note: Packages built this way cannot be 100% reliable, but it's a - constraint of publicly available packages and there is little - that can be done to change that. See - https://docs.chocolatey.org/en-us/community-repository/community-packages-disclaimer - to better understand the limitations of a publicly available - repository. - Download Location is Publicly Available? - You will need to download the runtime files from their official - location at runtime. Use `$url`/`$url64` and - `Install-ChocolateyPackage`/`Install-ChocolateyZipPackage` in - tools\chocolateyInstall.ps1. - Download Location is Not Publicly Available? - Stop here, you can't push this to the community repository. You - can ask the vendor for permission to embed, then include a PDF of - that signed permission directly in the package. Otherwise you - will need to seek alternate locations to non-publicly host the - package. - Download Location Is Same For All Versions? - You still need to point to those urls, but you may wish to set up - something like Automatic Updater (AU) so that when a new version - of the software becomes available, the new package version - automatically gets pushed up to the community repository. See - https://docs.chocolatey.org/en-us/create/automatic-packages#automatic-updater-au - -2. Determine Package Type: - -- Installer Package - contains an installer (everything in template is - geared towards this type of package) -- Zip Package - downloads or embeds and unpacks archives, may unpack - and run an installer using `Install-ChocolateyInstallPackage` as a - secondary step. -- Portable Package - Contains runtime binaries (or unpacks them as a - zip package) - cannot require administrative permissions to install - or use -- Config Package - sets config like files, registry keys, etc -- Extension Package - Packages that add PowerShell functions to - Chocolatey - https://docs.chocolatey.org/en-us/features/extensions -- Template Package - Packages that add templates like this for `choco - new -t=name` - https://docs.chocolatey.org/en-us/guides/create/create-custom-package-templates -- Other - there are other types of packages as well, these are the main - package types seen in the wild - -3. Fill out the package contents: - -- tools\chocolateyBeforeModify.ps1 - remove if you have no processes - or services to shut down before upgrade/uninstall -- tools\LICENSE.txt / tools\VERIFICATION.txt - Remove if you are not - embedding binaries. Keep and fill out if you are embedding binaries - in the package AND pushing to the community repository, even if you - are the author of software. The file becomes easier to fill out - (does not require changes each version) if you are the software - vendor. If you are building packages for internal use (organization, - etc), you don't need these files as you are not subject to - distribution rights internally. -- tools\chocolateyUninstall.ps1 - remove if autouninstaller can - automatically uninstall and you have nothing additional to do during - uninstall -- Readme.txt - delete this file once you have read over and used - anything you've needed from here -- nuspec - fill this out, then clean out all the comments (you may wish - to leave the headers for the package vs software metadata) -- tools\chocolateyInstall.ps1 - instructions in next section. - -4. ChocolateyInstall.ps1: - -- For embedded binaries - use `$fileLocation` (`$file`/`$file64`) and - `Install-ChocolateyInstallPackage`/ `Get-ChocolateyUnzip`. -- Downloading binaries at runtime - use `$url`/`$url64` and - `Install-ChocolateyPackage` / `Install-ChocolateyZipPackage`. -- Other needs (creating files, setting registry keys), use regular - PowerShell to do so or see if there is a function already defined: - https://docs.chocolatey.org/en-us/create/functions -- There may also be functions available in extension packages, see - https://community.chocolatey.org/packages?q=id%3A.extension for examples and - availability. -- Clean out the comments and sections you are not using. - -5. Test the package to ensure install/uninstall work appropriately. - There is a test environment you can use for this - - https://github.com/chocolatey/chocolatey-test-environment - -6. Learn more about Chocolatey packaging - go through the workshop at - https://github.com/chocolatey/chocolatey-workshop - You will learn about - - General packaging - - Customizing package behavior at runtime (package parameters) - - Extension packages - - Custom packaging templates - - Setting up an internal Chocolatey.Server repository - - Adding and using internal repositories - - Reporting - - Advanced packaging techniques when installers are not friendly to - automation - -7. Delete this file. diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/organizeit.cli.1.0.0.nupkg b/OrganizeIt.Cli/OrganizeIt.Cli/organizeit.cli.1.0.0.nupkg deleted file mode 100644 index 07f17cc..0000000 Binary files a/OrganizeIt.Cli/OrganizeIt.Cli/organizeit.cli.1.0.0.nupkg and /dev/null differ diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/tools/LICENSE.txt b/OrganizeIt.Cli/OrganizeIt.Cli/tools/LICENSE.txt deleted file mode 100644 index 3b1a53f..0000000 --- a/OrganizeIt.Cli/OrganizeIt.Cli/tools/LICENSE.txt +++ /dev/null @@ -1,11 +0,0 @@ - -Note: Include this file if including binaries you have the right to distribute. -Otherwise delete. this file. - -===DELETE ABOVE THIS LINE AND THIS LINE=== - -From: <insert applicable license url here> - -LICENSE - -<Insert License Here> diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/tools/VERIFICATION.txt b/OrganizeIt.Cli/OrganizeIt.Cli/tools/VERIFICATION.txt deleted file mode 100644 index 5b13942..0000000 --- a/OrganizeIt.Cli/OrganizeIt.Cli/tools/VERIFICATION.txt +++ /dev/null @@ -1,13 +0,0 @@ - -Note: Include this file if including binaries you have the right to distribute. -Otherwise delete. this file. If you are the software author, you can mention -this. - -===DELETE ABOVE THIS LINE AND THIS LINE=== - -VERIFICATION -Verification is intended to assist the Chocolatey moderators and community -in verifying that this package's contents are trustworthy. - -<Include details of how to verify checksum contents> -<If software vendor, explain that here> \ No newline at end of file diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateybeforemodify.ps1 b/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateybeforemodify.ps1 deleted file mode 100644 index eadc55f..0000000 --- a/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateybeforemodify.ps1 +++ /dev/null @@ -1,9 +0,0 @@ -# This runs before upgrade or uninstall. -# Use this file to do things like stop services prior to upgrade or uninstall. -# NOTE: It is an anti-pattern to call chocolateyUninstall.ps1 from here. If you -# need to uninstall an MSI prior to upgrade, put the functionality in this -# file without calling the uninstall script. Make it idempotent in the -# uninstall script so that it doesn't fail when it is already uninstalled. -# NOTE: For upgrades - like the uninstall script, this script always runs from -# the currently installed version, not from the new upgraded package version. - diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateyinstall.ps1 b/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateyinstall.ps1 deleted file mode 100644 index 7ecef6b..0000000 --- a/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateyinstall.ps1 +++ /dev/null @@ -1,10 +0,0 @@ -$packageName = 'organizeit.cli' -$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" -$binRoot = Get-ToolsLocation - -$targetPath = Join-Path $binRoot $packageName - -Install-ChocolateyZipPackage $packageName 'https://github.com/Toyin5/OrganizeIt/archive/refs/tags/v.1.0.1.zip' $toolsDir - -# Create a shortcut to the executable -Install-ChocolateyShortcut -shortcutFilePath "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\OrganizeIt.Cli.lnk" -targetPath "$targetPath\organizeit.cli.exe" \ No newline at end of file diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateyuninstall.ps1 b/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateyuninstall.ps1 deleted file mode 100644 index 8f3ef1d..0000000 --- a/OrganizeIt.Cli/OrganizeIt.Cli/tools/chocolateyuninstall.ps1 +++ /dev/null @@ -1,78 +0,0 @@ -# IMPORTANT: Before releasing this package, copy/paste the next 2 lines into PowerShell to remove all comments from this file: -# $f='c:\path\to\thisFile.ps1' -# gc $f | ? {$_ -notmatch "^\s*#"} | % {$_ -replace '(^.*?)\s*?[^``]#.*','$1'} | Out-File $f+".~" -en utf8; mv -fo $f+".~" $f - -## NOTE: In 80-90% of the cases (95% with licensed versions due to Package Synchronizer and other enhancements), -## AutoUninstaller should be able to detect and handle registry uninstalls without a chocolateyUninstall.ps1. -## See https://docs.chocolatey.org/en-us/choco/commands/uninstall -## and https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateypackage - -## If this is an MSI, ensure 'softwareName' is appropriate, then clean up comments and you are done. -## If this is an exe, change fileType, silentArgs, and validExitCodes - -$ErrorActionPreference = 'Stop' # stop on all errors -$packageArgs = @{ - packageName = $env:ChocolateyPackageName - softwareName = 'OrganizeIt.Cli*' #part or all of the Display Name as you see it in Programs and Features. It should be enough to be unique - fileType = 'EXE_MSI_OR_MSU' #only one of these: MSI or EXE (ignore MSU for now) - # MSI - silentArgs = "/qn /norestart" - validExitCodes= @(0, 3010, 1605, 1614, 1641) # https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx - # OTHERS - # Uncomment matching EXE type (sorted by most to least common) - #silentArgs = '/S' # NSIS - #silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP-' # Inno Setup - #silentArgs = '/s' # InstallShield - #silentArgs = '/s /v"/qn"' # InstallShield with MSI - #silentArgs = '/s' # Wise InstallMaster - #silentArgs = '-s' # Squirrel - #silentArgs = '-q' # Install4j - #silentArgs = '-s -u' # Ghost - # Note that some installers, in addition to the silentArgs above, may also need assistance of AHK to achieve silence. - #silentArgs = '' # none; make silent with input macro script like AutoHotKey (AHK) - # https://community.chocolatey.org/packages/autohotkey.portable - #validExitCodes= @(0) #please insert other valid exit codes here -} - -[array]$key = Get-UninstallRegistryKey -SoftwareName $packageArgs['softwareName'] - -if ($key.Count -eq 1) { - $key | % { - $packageArgs['file'] = "$($_.UninstallString)" #NOTE: You may need to split this if it contains spaces, see below - - if ($packageArgs['fileType'] -eq 'MSI') { - # The Product Code GUID is all that should be passed for MSI, and very - # FIRST, because it comes directly after /x, which is already set in the - # Uninstall-ChocolateyPackage msiargs (facepalm). - $packageArgs['silentArgs'] = "$($_.PSChildName) $($packageArgs['silentArgs'])" - - # Don't pass anything for file, it is ignored for msi (facepalm number 2) - # Alternatively if you need to pass a path to an msi, determine that and - # use it instead of the above in silentArgs, still very first - $packageArgs['file'] = '' - } else { - # NOTES: - # - You probably will need to sanitize $packageArgs['file'] as it comes from the registry and could be in a variety of fun but unusable formats - # - Split args from exe in $packageArgs['file'] and pass those args through $packageArgs['silentArgs'] or ignore them - # - Ensure you don't pass double quotes in $file (aka $packageArgs['file']) - otherwise you will get "Illegal characters in path when you attempt to run this" - # - Review the code for auto-uninstaller for all of the fun things it does in sanitizing - https://github.com/chocolatey/choco/blob/bfe351b7d10c798014efe4bfbb100b171db25099/src/chocolatey/infrastructure.app/services/AutomaticUninstallerService.cs#L142-L192 - } - - Uninstall-ChocolateyPackage @packageArgs - } -} elseif ($key.Count -eq 0) { - Write-Warning "$packageName has already been uninstalled by other means." -} elseif ($key.Count -gt 1) { - Write-Warning "$($key.Count) matches found!" - Write-Warning "To prevent accidental data loss, no programs will be uninstalled." - Write-Warning "Please alert package maintainer the following keys were matched:" - $key | % {Write-Warning "- $($_.DisplayName)"} -} - -## OTHER POWERSHELL FUNCTIONS -## https://docs.chocolatey.org/en-us/create/functions -#Uninstall-ChocolateyZipPackage $packageName # Only necessary if you did not unpack to package directory - see https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyzippackage -#Uninstall-ChocolateyEnvironmentVariable - https://docs.chocolatey.org/en-us/create/functions/uninstall-chocolateyenvironmentvariable -#Uninstall-BinFile # Only needed if you used Install-BinFile - see https://docs.chocolatey.org/en-us/create/functions/uninstall-binfile -## Remove any shortcuts you added in the install script. - diff --git a/OrganizeIt.Cli/organizeit.1.0.0.nupkg b/OrganizeIt.Cli/organizeit.1.0.0.nupkg new file mode 100644 index 0000000..8bde667 Binary files /dev/null and b/OrganizeIt.Cli/organizeit.1.0.0.nupkg differ diff --git a/OrganizeIt.Cli/OrganizeIt.Cli/organizeit.cli.nuspec b/OrganizeIt.Cli/organizeit.cli.nuspec similarity index 55% rename from OrganizeIt.Cli/OrganizeIt.Cli/organizeit.cli.nuspec rename to OrganizeIt.Cli/organizeit.cli.nuspec index 8ccc0de..c5a51c5 100644 --- a/OrganizeIt.Cli/OrganizeIt.Cli/organizeit.cli.nuspec +++ b/OrganizeIt.Cli/organizeit.cli.nuspec @@ -1,18 +1,21 @@ <?xml version="1.0" encoding="utf-8"?> -<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd"> +<package> <metadata> - <id>organizeit.cli</id> + <id>organizeit</id> <version>1.0.0</version> - <title>OrganizeIt.Cli (Install) + OrganizeIt Toyin Muhammed https://github.com/Toyin5/OrganizeIt - organizeit.cli file organization OrganizeIt.Cli is a command-line tool designed to help you organize files in a specified directory based on a configuration file. OrganizeIt.Cli is a command-line tool designed to help you organize files in a specified directory based on a configuration file. It supports custom configuration files and provides feedback on the success or failure of the organization process. - https://opensource.org/licenses/MIT - true + organizeit cli files organization folders directories + Copyright 2024 Toyin Muhammed + https://github.com/Toyin5/OrganizeIt#license + false + https://github.com/Toyin5/OrganizeIt/releases - + + \ No newline at end of file