Home/ Questions/Q 3425998
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T06:39:40+00:00

I have published an app using ClickOnce for about a year with relatively few

  • 0

I have published an app using ClickOnce for about a year with relatively few issues.

This week I am off site, but needed to make some changes to the app and the way the autoupdate works – so I am publishing to the IIS of my local machine rather than the normal distribution server for testing. The wierd thing is that as of yesterday afternoon, I started receiving the warning

Published version 2.1.3.18 already exists on the server, do you want to overwrite it

But the version i am publishing is way beyond that (2.1.3.32 currently), so I shouldn’t be receiving the warning at all.

Frankly, it’s not hurting anything, I can choose yes and publish over it without any problem, but I would like to know what is happening. Does anybody have any idea?

Thanks!

EDIT FOR CLARIFICATION
2.1.3.18 is on the server, but I am publishing versions greater than that version, so I should not be warned. The last version I published was 2.1.3.32.

The version number I am referring to above is the Publish Version from the Publish tab of VS2008, not the Assembly Version.

MORE INFO
I just opened my MYApp.Application file with MageUI and it says the version is 2.1.3.18. I deleted the file, recompiled and published. New file has the exact same version. Yet when I look under my VS Publish tag, it says Deployment Version is 2.1.3.33.

Where is VS pulling the 2.1.3.18 number from when building my manifest??

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I just had the same problem today, Just do a “Clean” on the project and then publish again (right click over project icon in solution explorer then Clean). This worked for me.

    • 0