Trying to convert PSADT 3.10.2 to PSADT 4.1.3 but getting error: Convert-ADTDeployment : Cannot determine line endings as the text probably contain mixed line endings

The Toolkit Toolkit Features
1

This part analyzes seems showing what is changed so this works:

Test-ADTCompatibility -FilePath "C:\temp\think-cellv13.0.35.752(32-bit)EN\Deploy-Application.ps1" -Format Grid

and convert the PackageFolder gives an error:

Convert-ADTDeployment -Path "C:\temp\think-cellv13.0.35.752(32-bit)EN"

Convert-ADTDeployment : Cannot determine line endings as the text probably contain mixed line endings.
Parameter name: text
At line:1 char:1

  • Convert-ADTDeployment -Path "C:\temp\think-cellv13.0.35.752(32-bit)EN ...
  •   + CategoryInfo          : NotSpecified: (:) [Convert-ADTDeployment], ArgumentException
  + FullyQualifiedErrorId : System.ArgumentException,Convert-ADTDeployment

Any comment or insight are welcome, thank you in advance

btw I am not sure where it is better top post this under toolkit feature or general discussions?

2

The converter hasn't been updated to 4.1.x yet unfortunately. You can convert your existing script to 4.0.x perhaps, then manually adjust a few things for 4.1.x.

1 Like
3

Thank you for the fast reply!
I think I will upgrade it manually for now, but will try again if convert will be updated to support PSADT 4.1.3, for there is many packages that need to be lifted up :smiley:

4

I'm having the same issue here however using PSADT 4.0.6 powershell module. Exact same behaviour in that Test-ADTCompatibility works but Convert-ADTDeployment doesnt. Am I correct in thinking that the PSADT PS Module is what determines what version it trys to convert to?

5

There's many things to unpack here.

  1. The forums are not the replace to report bugs. Bugs for this should be ported on GitHub appropriately: GitHub · Where software is built
  2. This auxiliary module is very much in beta, hence why it's version number isn't even at 1.0 yet. As such, especially if your script isn't complex, I'd recommend just manually converting it.
  3. Discussing the product here is not ideal as @DanGough doesn't frequent these forums regularly so he will not see the posts.
  4. While I'm heavily involved with PSAppDeployToolkit, I've had no involvement with PSAppDeployToolkit.Tools and can't really explain much about it without digging into things myself.
  5. The PSAppDeployToolkit.Tools module is provided with no promises or guarantees. @DanGough works on this in his spare time amongst his full-time job and family life, so patches and fixes should not be expected at the frequency in which they're applied to the underlying PSAppDeployToolkit project.

If there's anything else I can assist with, I'm definitely happy to but there's probably not much more I can offer regarding the PSAppDeployToolkit.Tools module for the aforementioned reasons.

1 Like