I have a simple batch file that I'm running from a DOS command line that is used for building a small C# application that publishes a ClickOnce project. One line is this:
msbuild MyApp.csproj /t:publish /property:PublishDir="deploy/"
This currently publishes the application, but it uses the Publish Version that I set up in Visual Studio's "Publish" tab. I'm hoping to be able to set the publish version at the command line, and specifically, I'd like to use the Assembly Version of the project. Something like:
msbuild MyApp.csproj /t:publish /property:PublishDir="deploy/" /property:PublishVersion="$(Proj.AssemblyVersion)"
I'm hoping to do without creating a custom task, since this is just an interim solution, and I will replace it with a more proper build system later.
Alternatively, I've looked at updating the published manifest version using the Mage Command Line Tool with the -Update
flag, but I did not know how to retrieve the assembly version number from the project or built assembly without using PowerShell or some program that would need to be downloaded. If I could use something that comes with Visual Studio, that would work as well.
Try adding this to your .csproj file. The target will retrieve the version from the output assembly and update the ApplicationVersion before the Publish:
<Target Name="AfterCompile">
<GetAssemblyIdentity AssemblyFiles="$(TargetPath)">
<Output TaskParameter="Assemblies" ItemName="fooAssemblyInfo"/>
</GetAssemblyIdentity>
<PropertyGroup>
<ApplicationVersion>%(fooAssemblyInfo.Version)</ApplicationVersion>
</PropertyGroup>
</Target>
There's probably a nicer way to dynamically get the assembly name but for your purpose it should do the trick.
Credit to this answer for the GetAssemblyIdentity
syntax:
https://stackoverflow.com/a/443364/266882
Questioner Edit:
See comment below for update.
msbuild xxx.csproj /target:clean;publish /property:ApplicationVersion=1.2.3.4
In order to correctly update the version declared in the deployment manifest you need to modify the ApplicationVersion at the "AfterCompile" step rather than the "BeforePublish" step, since the application manifest is generated at build time.
But then you can't rely on the $(TargetPath) property to point to the assembly and instead use the following path: $(ProjectDir)obj\$(ConfigurationName)\$(TargetFileName)
So here's the updated Target code snippet that you can add to the .csproj file:
<Target Name="AfterCompile">
<GetAssemblyIdentity AssemblyFiles="$(ProjectDir)obj\$(ConfigurationName)\$(TargetFileName)">
<Output TaskParameter="Assemblies" ItemName="AssemblyInfo" />
</GetAssemblyIdentity>
<PropertyGroup>
<ApplicationVersion>%(AssemblyInfo.Version)</ApplicationVersion>
</PropertyGroup>
</Target>