Home › How it works

packbit:
Four phases.
One process.

From an empty package to a deployed application

The same process for every application, whether it is a simple MSI or a vendor installer with a decade of accumulated quirks.

Phase 01 · Build

Build the package from blocks

Add the steps the installation actually needs: copy a file, run the setup, remove a shortcut. The sequence reads as a list, not as a page of script.

# Install sequence

≡Copy filepackbit\*.ini → backup

≡Run installersetup.exe · silent

≡Remove shortcutDesktop\packbit.lnk

Phase 02 · Configure

Set requirements, dependencies and behaviour

Requirements, dependencies, exit codes and install behaviour are values you fill in, not code you write. Whoever opens the package next reads the intent instead of reconstructing it.

# Configuration

≡Requirementarchitecture · OS version

≡Dependencyprerequisite package

≡Exit codessuccess · reboot required

Phase 03 · Migrate

Bring existing packages up to standard

Point the migration engine at the packages you already have. It analyzes each one, transforms it to the target standard, and lists the steps that still need a decision.

# Migration report

≡Transformed28 steps

≡Mapped6 reusable components

≡Needs review2 custom steps

Phase 04 · Deploy

Publish into the platform you already run

The result is a standard package. packbit publishes it straight into your deployment platform, or hands it to you to ship the way you already do. No new deployment infrastructure to stand up.

# Output

≡Packagestandard · PowerShell

≡Validation0 errors

≡Publishdeployment platform · ready

Built for PowerShell users

PowerShell, without the pain.

A visual layer over PowerShell, not a replacement for it

The blocks on the left produce the script on the right: the same script you would have written, every time, without the typos.

Low-code blocks● valid

# Backup configuration

≡IfTest-Path "$envProgramFilesX86\packbit\HwPlugin.ini"

≡Copy-ADTFile-Path … -Destination …

# Install the application

≡Start-ADTProcess-FilePath … -ArgumentList …

# Remove vendor shortcuts

≡Remove-ADTFile-Path "$envCommonDesktop\packbit.lnk"

Generated code previewPowerShell

## MARK: Install
# Backup configuration
if (Test-Path "$envProgramFilesX86\packbit\HwPlugin.ini") {
    Copy-ADTFile -Path "$envProgramFilesX86\packbit\HwPlugin.ini" `
                 -Destination "$envProgramData\packbit\packbit"
}

# Install the application
Start-ADTProcess -FilePath "$($adtSession.DirFiles)\setup.exe" `
                 -ArgumentList '/S /v"/qn REBOOT=ReallySuppress"'

## MARK: Post-Install
# Remove vendor shortcuts
Remove-ADTFile -Path "$envCommonDesktop\packbit.lnk"

Comfortable in PowerShell? Read the preview, edit it, take it further. Not comfortable in PowerShell? You never have to open it, and the package is still correct.

Stop scripting.
Start shipping.

The result is a standard PSADT package, published into the platform you deploy with.

Discover packbit See the migration engine

packbit:Four phases.One process.