A set of utilities that allow to autonomously build a Visual Studio SSIS project (dtproj) into a deployment package (ispac), and deploy the package to an SSIS catalog
Apache License 2.0
52
stars
39
forks
source link
Package versions not shown in @Project.manifest #15
While giving this tool a test drive and comparing against the outputs of the Visual Studio Build, I noticed that the @Project.manifest file versioning differs from that provided by the Visual Studio build.
For each .dtsx file in the @Project.manifest - the original tool enters the following into the parameters:
Always One (1)Always Zero (0)DTS:VersionBuild from the DTSX fileDTS:VersionGUID from the DTSX file
The parent (first) Versions on the Project leve in the @Project.manifest file remain with zeros in every parameter (this already works as expected):
000
Would it be possible to make this behave in this way - to align the behavior with the Visual Studio 2015 (SSDT 17.2 build number: 14.0.61707.300 - latest version at the time of writing)?
Thanks,
Peter
Hi Roman,
While giving this tool a test drive and comparing against the outputs of the Visual Studio Build, I noticed that the @Project.manifest file versioning differs from that provided by the Visual Studio build.
For each .dtsx file in the @Project.manifest - the original tool enters the following into the parameters: