Groups | Blog | Home
all groups > dotnet distributed apps > january 2006 >

dotnet distributed apps : Clickonce fails after weeks of success


Kenn
1/22/2006 4:42:01 PM
I have been using ClickOnce since the day I downloaded CSharp Express, with
great success.

I have 10 client machines that run my app. Today I published a new version
to the server using Visual Studio 2005 Standard (just purchased) and 7 of the
10 client machines do not see a change in the manifest.
Hence, do not load the newest version.


Steps I have taken:
1. I made a change to the code and rebuilt the project - then republished
2. I have cleared the IE cache on the client machines.
3. I have deleted all IE offline content on the client machines.
4. I have set IE on the client machines to check for new pages every visit
5. I have uninstalled the app on the client machine completely and deleted
the 2.0 folder it left behind, then reinstalled from the server (Publish.htm
shows the correct version I want)
6. I have deleted the user (draconian I know) and resetup the user on the
client machine
7. I have turned off ISAPI caching on the distribution web server
8. I have restarted IIS several times
9. I have rebooted the web server serveral times
10. I have deleted the original website and all the previous versions and
republished


After all this the client machines still load an older version, which is NOT
even on the website an longer.

This is a major bug. It will definately affect how I propose the use of
ClickOnce to clients unless there is a simple fix for this problem.

Thanks for your help,

Kenn



Kenn
1/23/2006 5:55:02 AM
I believe I have found the issue.

The proxy server on the client site may be caching the old versions.

I will report back if this was the issue.

Thanks,

Kenn

[quoted text, click to view]
Rune Huseby
1/24/2006 12:55:58 PM
"=?Utf-8?B?S2Vubg==?=" <Kenn@discussions.microsoft.com> wrote in
news:40D255E1-A1F6-4C45-B1B7-1DD1E88DA1AF@microsoft.com:

[quoted text, click to view]

If you add this custom header to your IIS-server, where you store your app,
proxy and cache-servers should be less of a problem:
Cache-Control: private


--
AddThis Social Bookmark Button