drjohnt / publishdacpac Goto Github PK

Hello sir,

When I attempt to use the parameter -DeployScriptPath I receive the following error message:

9 | … \MSSQLLocalDB" -Database: "G1Lifecycle_RMS" -DeployScriptPath "c:\tem …
| ~~~~~~~~~~~~~~~~~
| A parameter cannot be found that matches parameter name 'DeployScriptPath'.

Am I missing something? Most of the parameters appear as soon as I type "-" but some don't like -DeployScriptPath.

Please let me know what I can do to correct this error.

Many thanks in advance!

~ Dave

patchfile.txt

Save() silently fails if the path to the publish file is not absolute. For my purposes, I overwrite the publish file, but the previous behavior should work too.

(Great work on this repo!)

Currently, you only support the following arguments for publishing using SQLpackage.exe as per this script:

/Action:Publish
/SourceFile:$DacPacPath
/Profile:$DacPacUpdatedProfilePath

Our use case does not play perfect with the profile.xml since depending on the environment, we'll need some different settings. There can be tens of different environments, all with different SQLCMD variable requirements.

Have you thought about allowing these combinations of arguments (source)?

/Action:Publish
/SourceFile:$sourceFile
/TargetServerName:$targetServerName
/TargetDatabaseName:$targetDBname
/V:SQLCMDVariable1=$SQLCMDVariable1
/v:SQLCMDVariable2=$SQLCMDVariable2

I'll probably be implementing something close to this so if you're open to PRs and if you're not working on this already, I'll be glad to be of help.

Hi,

I'm reading through the source to audit it for my own peace of mind, and noticed, that:

"PublishDacPac.psd1#L93"

links to https://github.com/DrJohnT/PublishDacPac/releases/tag/1.1.0 but your GitHub releases only has 1.0.2, and the PowershellGallery has 1.1.1.

Am i seeing the latest source in GitHub?

Adding 160/16 to the various ValidateParameter calls allowed PublishDacPac to locate SqlPackage 16.x on my machine.