Skip to content

sqlpackage deployment script is recognized differently due to CR/LF. #588

Open
@sqlmvp

Description

@sqlmvp
  • SqlPackage or DacFx Version: SqlPackage 162.5.57.1
  • .NET Framework (Windows-only) or .NET Core: .NET Frameworkd and .NET Core
  • Environment (local platform and source/target platforms): Windows and Linux(docker)

Steps to Reproduce:
I am developing a deployment pipeline using SqlPackage. The build (creating a Nuget package) is done on a Windows server. The deployment is executed on a Linux container. When I generate a deployment script using the Action:Script command in SqlPackage, it recognizes that the versions are different due to the CR/LF problem, and recognizes it as a new version even though there are no changes.

  1. Create Nuget on Windows
    msbuild.exe" "${{ inputs.projectFile }}" /p:Configuration=Release /p:platform="any cpu" /p:OutputPath="${{ env.releasePath }})

  2. Create deploy script on Linux (Conteriner)
    sqlpackage /action:script
    /sf: DB.dacpac
    /pr:DB.publish.xml
    /op:output.sql
    /tsn:TARGET_SERVER_DOMAIN
    /tdn:TARGET_DB_NAME
    /tu:TARGET_USER_ID /ttsc:true
    /tp:TARGET_USER_PWD \

Did this occur in prior versions? If not - which version(s) did it work in?

(DacFx/SqlPackage/SSMS/Azure Data Studio)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions