 | |
Re: dotnet deployment using MSI / IE6
Dotnet Distributed Applications microsoft.public.dotnet.distributed_apps
 |
| | Thread Tools | Search this Thread | Display Modes |
#1
 
| |||
| |||
|
Re: dotnet deployment using MSI / IE6 -
06-25-2003
, 06:32 AM
|
From: "Joost Devos" <Joost.Devos (AT) weblications (DOT) be References: <uHCwYbbODHA.2316 (AT) TK2MSFTNGP12 (DOT) phx.gbl #$nTOrbODHA.560 (AT) TK2MSFTNGP10 (DOT) phx.gbl Subject: Re: dotnet deployment using MSI / IE6 Date: Mon, 23 Jun 2003 23:48:21 +0200 Lines: 91 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: <uItRuEdODHA.1712 (AT) TK2MSFTNGP12 (DOT) phx.gbl Newsgroups: microsoft.public.dotnet.distributed_apps,microsoft .public.dotnet.general,mic |
,microsoft.public.windows.inetexplorer.ie6.setup,m icrosoft.public.windows.ms
i
Quote:
|
NNTP-Posting-Host: 194.78.48.65 Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP12.phx.gbl Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:99210 microsoft.public.inetexplorer.ie4.setup:15629 |
microsoft.public.windows.inetexplorer.ie6.setup:34 703
microsoft.public.windows.msi:590
microsoft.public.dotnet.distributed_apps:5901
Quote:
|
X-Tomcat-NG: microsoft.public.dotnet.distributed_apps Hi Phil, Thanks for your help. Indeed I do change the package version and the product code during the MSI file creation, before putting the resulting MSI file onto the webserver but even then, the new MSI file doesn't download to the client... which is my major problem(RemovePreviousVersion is set to "true") I check the package version on the client in the Control Panel, Add/Remove programs, the link "support information" of the installed program. It doesn't change after retrying the link which references the new version of the MSI package.. So when I delete the IE cache and requery the same link again, only then it downloads and installs that new version. The problem is, I can't ask the installer to empty his personal IE cache each time before installing our upgrade... btw: IE version is 6.0.2800.1203 Any other suggestions ? TIA Joost "Phil Wilson" <phil.wilson (AT) unisys (DOT) spamcom> wrote in message news:%23$nTOrbODHA.560 (AT) TK2MSFTNGP10 (DOT) phx.gbl... You can't just reinstall the updated MSI file if it's got the same product code and package code because it will just go into repair mode and not even look at your new MSI file. I suspect that updating the version of the product, changing package code and product code, and setting RemovePreviousVersions is the easiest way for you to do an upgrade (that would be a major upgrade - other solutions involve patches or msiexec command line options). -- Phil Wilson [MVP Windows Installer] ---- "Joost Devos" <Joost.Devos (AT) weblications (DOT) be> wrote in message news:uHCwYbbODHA.2316 (AT) TK2MSFTNGP12 (DOT) phx.gbl... SITUATION: I use VisualStudio-2003 and a deployment project to create an .MSI file. I put that file on a public webserver then clients just access that file and install it locally using http://server/install.msi ==> This works fine the first time THEN: after making changes to the application source code, after recreation of the deployment project MSI file after putting it again on the public webserver clients just access that file and install it locally using http://server/install.msi ==> Download is extremely fast, in fact the version doesn't get updated locally !! FINDINGS Clients use IE6, the .MSI file is coming into the IE cache and the expires attribute initially was set to "none". So the next download from the webserver towards the IE clients doesn't happen. - I cleared the IE download cache files and cookies - I changed the settings in IE to download "on every visit to the page" - I changed the settings in the IIS headers for that MSI file, so that the "expires attribute" now becomes an hour less than the download hour. - the Version property of the deployment MSI file is changed every time so that I'm sure that a new version is created and available on the webserver ==> still, the MSI file is not downloaded and a cached version is used if I not manually delete the IE download cache I guess the problem is situated in IE and its local cache. It seems that IE doesn't take into account its own "expires" attribute... How can I prevent this from happen, so that the clients always get the latest version available from the webserver ? What do I overlook here ?? TIA Joost Devos |
#2
| ||||
| ||||
|
|
From: "Joost Devos" <Joost.Devos (AT) weblications (DOT) be References: <uHCwYbbODHA.2316 (AT) TK2MSFTNGP12 (DOT) phx.gbl #$nTOrbODHA.560 (AT) TK2MSFTNGP10 (DOT) phx.gbl |
<0uOmUUwODHA.2584 (AT) cpmsftngxa06 (DOT) phx.gbl>
Quote:
|
Subject: Re: dotnet deployment using MSI / IE6 Date: Fri, 27 Jun 2003 23:21:40 +0200 Lines: 34 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: <Oa2mbIPPDHA.3236 (AT) TK2MSFTNGP10 (DOT) phx.gbl Newsgroups: microsoft.public.dotnet.distributed_apps,microsoft .public.dotnet.general,mic |
,microsoft.public.windows.inetexplorer.ie6.setup,m icrosoft.public.windows.ms
i
Quote:
|
NNTP-Posting-Host: 194.78.48.65 Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:99672 microsoft.public.inetexplorer.ie4.setup:15630 |
microsoft.public.windows.inetexplorer.ie6.setup:34 916
microsoft.public.windows.msi:606
microsoft.public.dotnet.distributed_apps:5965
Quote:
|
X-Tomcat-NG: microsoft.public.dotnet.distributed_apps Hi Bradley, Tx for your assistance. No, it doesn't help me. The installer now gives me the following error: A network error occured while attempting to read from the file http://server/share/package[1].msi Any other suggestions ?? The only thing that works is manually "deleting the IE cache files..." before calling the link... regards Joost "Bradley Jiang[MSFT]" <bradleyj (AT) online (DOT) microsoft.com> wrote in message news:0uOmUUwODHA.2584 (AT) cpmsftngxa06 (DOT) phx.gbl... Hi, Please try the following command line instead of the http address directly: msiexec /i http://server/share/package.msi Check to see if it works. Best regards, Bradley Jiang This posting is provided "AS IS" with no warranties, and confers no rights. |
#3
| ||||
| ||||
|
|
From: "Joost Devos" <Joost.Devos (AT) weblications (DOT) be References: <uHCwYbbODHA.2316 (AT) TK2MSFTNGP12 (DOT) phx.gbl #$nTOrbODHA.560 (AT) TK2MSFTNGP10 (DOT) phx.gbl |
<0uOmUUwODHA.2584 (AT) cpmsftngxa06 (DOT) phx.gbl>
<Oa2mbIPPDHA.3236 (AT) TK2MSFTNGP10 (DOT) phx.gbl>
<zweM7kvPDHA.1724 (AT) cpmsftngxa09 (DOT) phx.gbl>
Quote:
|
Subject: Re: dotnet deployment using MSI / IE6 Date: Mon, 30 Jun 2003 18:21:28 +0200 Lines: 56 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 x-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: <OedYrOyPDHA.3236 (AT) TK2MSFTNGP10 (DOT) phx.gbl Newsgroups: microsoft.public.dotnet.distributed_apps,microsoft .public.dotnet.general,mic |
,microsoft.public.windows.inetexplorer.ie6.setup,m icrosoft.public.windows.ms
i
Quote:
|
NNTP-Posting-Host: 194.78.48.65 Path: cpmsftngxa09.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl Xref: cpmsftngxa09.phx.gbl microsoft.public.dotnet.general:14217 microsoft.public.inetexplorer.ie4.setup:68 |
microsoft.public.windows.inetexplorer.ie6.setup:64 49
microsoft.public.windows.msi:617
microsoft.public.dotnet.distributed_apps:1558
Quote:
|
X-Tomcat-NG: microsoft.public.dotnet.distributed_apps Hi Bradley, Tx again for your assistance. The error was: A network error occured while attempting to read from the file http://server/share/package[1].msi I think I know where the specified error is coming from: - If one first installs the MSI using IE, one needs to continue to update from IE and not using the MSIEXEC command, or he gets the error mentioned above - If one first installs the MSI using MSIEXEC, one needs to continue to update using MSIEXEC and not IE, or he gets a similer error as the one mentioned above This behavior is reproducable ! However, both installation methods used, suffer from the EXTRA problem that, if the MSI file is a newer version (eg. 1.0.0002) on the webserver and eg. version 1.0.0001 on the client, they both directly show the "Repair/Uninstall" window instead of installing the newer version above the older one ! And oh miracle, when one clears the IE cache and then tries (in both cases) to install the MSI again, the latest version from the webserver gets downloaded and installed !! How comes ?? Thanks in advance Joost Devos "Bradley Jiang[MSFT]" <bradleyj (AT) online (DOT) microsoft.com> wrote in message news:zweM7kvPDHA.1724 (AT) cpmsftngxa09 (DOT) phx.gbl... Hi Joost, Do you mean that if you clear up IE cache, we can run "msiexec /i http://server/share/package.msi" again successfully? Also, you may generate a verbose log to check the details. Run msiexec /i http://server/share/package.msi /lv C:\log.txt and you will create a C:\log.txt file. Check the log file for the details. Best regards, Bradley Jiang This posting is provided "AS IS" with no warranties, and confers no rights. |
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.