Using the Package Conversion Script - Using the Package Conversion Script - The PackageConversionScript.ps1 is a PowerShell script that converts an old unsigned package (non-password protected zip files consist of one projectsettings.xml file and one PSWDisplayText.sql file in it) to a new format (consist of two xml files) unsigned package structure. The script is provided with the installer folder with a separate directory called PackageConversionScript . - Brainware - Solution Configuration Manager - Brainware/Solution-Configuration-Manager/25.2/Solution-Configuration-Manager-Installation-Guide/Using-the-Package-Conversion-Script - 25.2 - 25.2

The PackageConversionScript.ps1 is a PowerShell script that converts an old unsigned package (non-password protected zip files consist of one projectsettings.xml file and one PSWDisplayText.sql file in it) to a new format (consist of two xml files) unsigned package structure. The script is provided with the installer folder with a separate directory called PackageConversionScript.

1. Press Windows + X and from the menu select Windows PowerShell or Windows Terminal. The Windows Powershell command screen is displayed.
2. Use the cd command to navigate to the directory where the PackageConversionScript.ps1 is located. Example: cd C:\path\to\PackageConversionScript
3. Execute the script: .\PackageConversionScript.ps1 -packageToConvert "C:\path\to\old_package.zip" -convertedPkgPath "C:\path\to\new_package.zip
   • packageToConvert (Required): Path to the old zip package that contains the projectsettings.xml and PSWDisplayText.sql files.
   • convertedPkgPath (Optional): Path where the new converted zip package will be saved. If this parameter is not provided, the new package will be saved in the same folder as the script with the name Converted.zip.

   CAUTION: If a package with the same name already exists in the output folder, it will be deleted before the new package is generated.
   Example:

   Old Package:A zip file named old_package.zip containing

   • projectsettings.xml
   • PSWDisplayText.sql

   Command: .\PackageConversionScript.ps1 -packageToConvert "C:\packages\old_package.zip" -convertedPkgPath "C:\packages\new_package.zip"

   Output

   The script will generate a new zip file new_package.zip containing:

   • projectsettings.xml
   • PSWDisplayText.xml (the converted file from PSWDisplayText.sql).

   Note:

   • This script convert only one old SCM compatible Package to a new format package at a time.
   • This script supports only generic structure of PSWDisplayText.sql file. It must only have insert queries for the PSWDisplayText table only. Each insert command must be in a new line. Multiple insert commands in a single line are not supported. Line breaks (new line characters) are not supported for any DisplayText value.
   • This script does not sign packages. It simply converts the old unsigned package format to the new format.
   • If a package with the same name exists at the specified OutputPath, it is deleted before generating the new converted package.
   • If the OldPackagePath is invalid or the required files (projectsettings.xml or PSWDisplayText.sql) are missing, the script will throw an error and stop executing.
   • Users need to have admin privileges to run the script file.
   • Do not include spaces in the folder names within the path specified for “packageToConvert” and “convertedPkgPath”.
   • When this converted package is imported in SCM, it triggers an alert. You must ensure that the unsigned package and all its files are scanned fully for safety and then proceed with the upload.

   

   The PackageConversionScript.ps1 simplifies the process of converting old unsigned packages to a new format. By following the instructions in this topic, you can easily generate the new converted package. If you encounter any errors, ensure that your input files are valid and present in the correct format.