Oct 18, 2011 at 9:09 PM
Edited Oct 18, 2011 at 9:17 PM
I have a package, which adds a clickonce application to a website (users can start the clickonce application from a page in the website).
This packages contains the clickonce application files inside the Content/Clickonce folder.
When first installed , all files are installed correctly.
When when I need to update the clickonce application, the .application file does not get updated, its skipped.
However, it should be updated because the manifest contains the new version number of the clickonce application. Failing to update this file
means, people won't see there is an update for the clickonce application.
The Application Files directory for the clickonce application is no issue, because each version is put inside a folder containing the version (standard behaviour of clickonce publishing).
Any idea how the update can be forced on certain files? I thought nuget should only skip files when they have been changed, but I'm pretty sure the .application was not changed manually.
Update: now you have <files> section in nuspec, maybe add <filesReplace> section for files which should always be replaced ... ?