I already talked about this topic in a previous post, Building ClickOnce with TeamCity, which was about .NET framework 3.5. This time I will talk about .NET framework 4.
As always when you change from one .NET framework version to another, there are some more things to install on our build server than just the .NET Framework.
Tonight we got the following issue on our TeamCity build server which produce different ClickOnce setups :
c:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets(3652, 9): error MSB3482: An error occurred while signing: Failed to sign ....\Tests\Output\bin\DeployClickOnce\app.publish\setup.exe.
The other day I published different posts about the way I automated our build process at Innoveo Solutions to generate different ClickOnce setup using TeamCity:
Build multiple ClickOnce deployment packages using MSBuild and Team City
The other day I posted about Build ClickOnce deployment packages using MSBuild and Team City, and there were some things that I didn’t like in my way of doing it.
I have multiple ClickOnce deployment packages created using TeamCity and MSBuild but each ClickOnce package has its own Application Revision due to the usage of TeamCity BUILD_NUMBER server build property.