I am not really sure about publishversion (in clickonce) and (application.)productversion. When do I use each one?

Should these be identical for application releases?

if I want to display version information under help | about, I think it would be preferable to use publishversion. Is this right? How do I do this?

Am I supposed to manually set them to be the same?

Thanks

They are seperate version numbers.   Product verison is the version of the actual binary deployed, publish version is the higher level version # for this deployment of the application.   It usually makes sense to keep them in sync, but you don't have to.  

If the application is deployed via ClickOnce, I would recommend displaying the publish version.  

[assembly: AssemblyVersion("1.0.*")]

my app version is currently 1.0.19.19234 or something. How do I change this?

Do I have to manually sync them, or can it be automated?

I think I really need some sort of overview, but cannot find one on MSDN.

Thanks

The problem I see with this is that it looks like the line:

Will error in the debug, simply because the application is not installed. Yet the information on the last published version is available in the Publish tab. Anyone know how to tell if the code is being run in the debug environment so that this can be "IF'd" out.

thanks

Is there any way it can be kept in sync?

I don't like the idea that the publish version revision is incrementing but the assembly version revision is not. What if I publish twice a day and assembly version will be the same but publish version will not be and there will be a breaking change. Won't it bind to an incompatible assembly? Should I just avoid setting revision for AssemblyVersion? But then 1.1.60118.0 looks ugly with the zero at the end..

Thanks!
RGab