Packages that can contain one (or maybe more than one) build version, however, only the latest build is ever deployed. Build version is never recorded to the schemaversions table: every script is stored without a build prefix.
Pretty much, your regular Install-DBOScript deployment from a folder, but stored as a package.
I'm not sure this one is really needed yet, as similar behavior could be achieved by using the same exact build version every time when such package is getting created, but we'll see.
Ideas so far:
- A new switch for New-DBOPackage (something like -Simple or -SingleBuild) that enables that behavior and enforces the version-less deployment history.
- Single-build packages seem to make more sense to avoid confusion during the deployment.
Packages that can contain one (or maybe more than one) build version, however, only the latest build is ever deployed. Build version is never recorded to the schemaversions table: every script is stored without a build prefix.
Pretty much, your regular Install-DBOScript deployment from a folder, but stored as a package.
I'm not sure this one is really needed yet, as similar behavior could be achieved by using the same exact build version every time when such package is getting created, but we'll see.
Ideas so far: