ClickOnce应用自动更新异常：C#企业内网自更新版本检测问题

I’ve tackled this exact problem countless times for internal enterprise apps using ClickOnce deployment. Let’s break down the key settings you need to verify, step by step, to get your updates detected properly.

1. Verify Assembly Information Versioning #

• Always increment the version number every time you republish. Head to your project properties → Application → Assembly Information, and make sure both Assembly Version and Assembly File Version are set to a higher value than the previous release (e.g., jump from 1.0.0.0 to 1.0.0.1).
• Skip relying on auto-increment for build/revision numbers unless you’ve got it locked in—manual increments are safer for controlled enterprise releases, where you need full visibility into version changes.
• Quick note: ClickOnce uses the Publish Version for update checks first, but mismatched assembly versions can muddle logging and deployment manifest consistency, so keep them aligned when possible.

2. Validate Publish Configuration #

• Double-check your publish target path: Go to Project Properties → Publish → Publish Location. This must be a network share or intranet URL every client machine can access (like \\corp-file-server\app-deployments\MyApp). If clients can’t reach this path, updates will never be detected.
• Ensure "Automatically generate deployment manifest" is checked. This .application file is the client’s primary reference for update checks—if it’s not regenerated with each publish, the app will keep reading stale data.
• When hitting "Publish", select "Replace existing files with new versions". Skipping this leaves old .manifest and .application files in place, which the client will prioritize over your new release.

3. Correct Publish - Update Settings #

• Navigate to Project Properties → Publish → Updates (click the "Updates..." button).
• Confirm the "Update location" matches your publish location exactly. Even a tiny typo (like a missing backslash or wrong server name) will break the entire detection flow.
• Enable update checking: Pick either "Check for updates before the application starts" or "Check for updates after the application starts"—without this toggle, the app won’t even attempt to look for new versions.
• If you’ve set a "Minimum required version", make sure your new publish version is strictly higher than this value. If it’s equal or lower, the client will ignore the update entirely.

4. Troubleshooting Quick Wins #

• Test intranet access: On a client machine, manually navigate to the publish/update location (open the network share in File Explorer). If you can’t see the latest .application file, it’s a permissions or network issue—loop in your IT team to ensure clients have read access to the share.
• Clear ClickOnce cache: Clients often cache old deployment data. Run this command in Command Prompt to wipe it:

  rundll32 dfshim CleanOnlineAppCache
  

• Check update logs: ClickOnce logs update attempts in %USERPROFILE%\AppData\Local\Apps\2.0 (look for folders with random alphanumeric names, then check the logs directory). You can also use Event Viewer → Windows Logs → Application to find errors tagged with "ClickOnce".

Give these steps a shot—most of the time, this issue boils down to a small configuration oversight or version mismatch. If you’re still stuck, share the exact version numbers and publish path details, and I can help dig deeper.

内容的提问来源于stack exchange，提问作者Stefan