Closed softwarecraft closed 6 years ago
When a project file (csproj) reloads after editing it, the assembly file/version numbers are reset to the initial values in OOTB format x.y.mmdd.nn, replacing the existing values, and this even though there is config to specify a different format:
<AssemblyInfo AssemblyInfoFiles="@(AssemblyInfoFiles)" AssemblyFileBuildNumberType="DateString" AssemblyFileBuildNumberFormat="yyMMdd" AssemblyFileRevisionType="AutoIncrement" AssemblyFileRevisionFormat="00" />
Using v4.0.11.0.
Full config:
<Import Project="$(MSBuildExtensionsPath)\ExtensionPack\4.0\MSBuild.ExtensionPack.VersionNumber.targets"/> <Target Name="Build" DependsOnTargets="AssemblyFileVersion" /> <Target Name="AssemblyFileVersion"> <Message Text="Update AssemblyFileVersion..." /> <ItemGroup> <AssemblyInfoFiles Include="Properties\AssemblyInfo.cs" /> </ItemGroup> <AssemblyInfo AssemblyInfoFiles="@(AssemblyInfoFiles)" AssemblyFileBuildNumberType="DateString" AssemblyFileBuildNumberFormat="yyMMdd" AssemblyFileRevisionType="AutoIncrement" AssemblyFileRevisionFormat="00" /> </Target>
When a project file (csproj) reloads after editing it, the assembly file/version numbers are reset to the initial values in OOTB format x.y.mmdd.nn, replacing the existing values, and this even though there is config to specify a different format:
Using v4.0.11.0.
Full config: