You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
<SSIS:Property SSIS:Name="VersionMajor">Always One (1)</SSIS:Property>
<SSIS:Property SSIS:Name="VersionMinor">Always Zero (0)</SSIS:Property>
<SSIS:Property SSIS:Name="VersionBuild">DTS:VersionBuild from the DTSX file</SSIS:Property>
<SSIS:Property SSIS:Name="VersionComments">
</SSIS:Property>
<SSIS:Property SSIS:Name="VersionGUID">DTS:VersionGUID from the DTSX file</SSIS:Property>
The parent (first) Versions on the Project leve in the @Project.manifest file remain with zeros in every parameter (this already works as expected):
<SSIS:Property SSIS:Name="VersionMajor">0</SSIS:Property>
<SSIS:Property SSIS:Name="VersionMinor">0</SSIS:Property>
<SSIS:Property SSIS:Name="VersionBuild">0</SSIS:Property>
<SSIS:Property SSIS:Name="VersionComments">
</SSIS:Property>
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
The text was updated successfully, but these errors were encountered:
pmalecka
added a commit
to pmalecka/ssis-build
that referenced
this issue
Mar 22, 2019
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:
<SSIS:Property SSIS:Name="VersionMajor">Always One (1)</SSIS:Property>
<SSIS:Property SSIS:Name="VersionMinor">Always Zero (0)</SSIS:Property>
<SSIS:Property SSIS:Name="VersionBuild">DTS:VersionBuild from the DTSX file</SSIS:Property>
<SSIS:Property SSIS:Name="VersionComments">
</SSIS:Property>
<SSIS:Property SSIS:Name="VersionGUID">DTS:VersionGUID from the DTSX file</SSIS:Property>
The parent (first) Versions on the Project leve in the @Project.manifest file remain with zeros in every parameter (this already works as expected):
<SSIS:Property SSIS:Name="VersionMajor">0</SSIS:Property>
<SSIS:Property SSIS:Name="VersionMinor">0</SSIS:Property>
<SSIS:Property SSIS:Name="VersionBuild">0</SSIS:Property>
<SSIS:Property SSIS:Name="VersionComments">
</SSIS:Property>
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
The text was updated successfully, but these errors were encountered: