MSDeploy 3和dbDacFx无法识别其声称支持的参数。我错过什么了吗？

这是我的命令行：

msdeploy.exe -verb:sync  -Source:dbDacFx="C:\MyDB.dacpac" -dest:dbDacFx="Data Source=myserver;Database=MyDB;userid=myuser;password=secret",wmsvc="https://www.myserver.com",username=myotheruser,password=anothersecret,BlockOnPossibleDataLoss="False" -verbose

存在该BlockOnPossibleDataLoss参数会导致此错误：

Error Code: 109
More Information:
Error: Exception has been thrown by the target of an invocation.
Error: Provider 'dbDacFx' does not support setting 'BlockOnPossibleDataLoss'.
Error count: 1.

如果我去掉BlockOnPossibleDataLoss参数，它可以正常工作

如果我放入这样的垃圾设置：

msdeploy.exe -verb:sync  -Source:dbDacFx="C:\MyDB.dacpac" -dest:dbDacFx="Data Source=myserver;Database=MyDB;userid=myuser;password=secret",wmsvc="https://www.myserver.com",username=myotheruser,password=anothersecret,asdfghjkl="False" -verbose

我收到以下错误消息：

Error: The provider 'dbDacFx' does not support the 'asdfghjkl' setting. Supporte
d settings are (dropDestinationDatabase, dacpacAction, includeData, commandTimeo
ut, AllowDropBlockingAssemblies, AllowIncompatiblePlatform, BackupDatabaseBefore
Changes, BlockOnPossibleDataLoss, BlockWhenDriftDetected, CommentOutSetVarDeclar
ations, CompareUsingTargetCollation, CreateNewDatabase, DeployDatabaseInSingleUs
erMode, DisableAndReenableDdlTriggers, DoNotAlterChangeDataCaptureObjects, DoNot
AlterReplicatedObjects, DropConstraintsNotInSource, DropDmlTriggersNotInSource,
DropExtendedPropertiesNotInSource, DropIndexesNotInSource, DropObjectsNotInSourc
e, DropPermissionsNotInSource, DropRoleMembersNotInSource, GenerateSmartDefaults
, IgnoreAnsiNulls, IgnoreAuthorizer, IgnoreColumnCollation, IgnoreComments, Igno
reCryptographicProviderFilePath, IgnoreDdlTriggerOrder, IgnoreDdlTriggerState, I
gnoreDefaultSchema, IgnoreDmlTriggerOrder, IgnoreDmlTriggerState, IgnoreExtended
Properties, IgnoreFileAndLogFilePath, IgnoreFilegroupPlacement, IgnoreFileSize,
IgnoreFillFactor, IgnoreFullTextCatalogFilePath, IgnoreIdentitySeed, IgnoreIncre
ment, IgnoreIndexOptions, IgnoreIndexPadding, IgnoreKeywordCasing, IgnoreLockHin
tsOnIndexes, IgnoreLoginSids, IgnoreNotForReplication, IgnoreObjectPlacementOnPa
rtitionScheme, IgnorePartitionSchemes, IgnorePermissions, IgnoreQuotedIdentifier
s, IgnoreRoleMembership, IgnoreRouteLifetime, IgnoreSemicolonBetweenStatements,
IgnoreTableOptions, IgnoreUserSettingsObjects, IgnoreWhitespace, IgnoreWithNoche
ckOnCheckConstraints, IgnoreWithNocheckOnForeignKeys, IncludeCompositeObjects, I
ncludeTransactionalScripts, NoAlterStatementsToChangeClrTypes, PopulateFilesOnFi
leGroups, RegisterDataTierApplication, RunDeploymentPlanExecutors, ScriptDatabas
eCollation, ScriptDatabaseCompatibility, ScriptDatabaseOptions, ScriptDeployStat
eChecks, ScriptFileSize, ScriptNewConstraintValidation, ScriptRefreshModule, Tre
atVerificationErrorsAsWarnings, UnmodifiableObjectWarnings, VerifyCollationCompa
tibility, VerifyDeployment, authType, computerName, encryptPassword, includeAcls
, password, prefetchPayload, userName, wmsvc).
Error count: 1.

请注意，在关于不支持某些其他垃圾参数的错误消息中，它将BlockOnPossibleDataLoss作为支持的设置之一。这是完全矛盾的。此外，如果您只是询问dbDacFx提供程序它支持什么：

msdeploy.exe -Help -Source:dbDacFx

它列出了一系列设置，包括：

Provider Setting:  BlockOnPossibleDataLoss

   A true or false value for the 'BlockOnPossibleDataLoss'
   setting.

我从阅读有关dbDacFx和其他许多因其不完整而感到沮丧的用户的文章中了解到，它已经“未煮熟”。但这是我第一次意识到这种情况是多么荒谬，它报告说它不支持一个特定的参数，却把它列在它支持的参数中

这是要修复的，还是应该放弃dbDacFx？我错过什么了吗