Re: Install on top of old client version issues?
- From: "schneider" <abc@xxxxxxxxxxx>
- Date: Mon, 18 Sep 2006 13:41:06 -0500
Case 1:
Install Client 1.0 [with MSI]
Install Client 2.0 [with MSI]
Case 2:
Install Client 1.0 [with MSI]
Remove Client 1.0 [Add Remove Programs]
Install Client 2.0 [with MSI]
Sometimes with Case 1, I get strange issues, usually on some strange
machine. If I remove all the installs and only install the latest it works.
Case 2, always seems to work, just requires an extra step.
Thanks,
Schneider
"Phil Wilson" <pdjwilson@xxxxxxxxxxxxxx> wrote in message
news:u%23ou3JA2GHA.3476@xxxxxxxxxxxxxxxxxxxxxxx
What does "installing custom clients on top of an old version" mean? Ifyou
install something with an MSI package and then start changing the filesreplaced.
manually you risk a repair kicking in and restoring the files you
--old
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
"schneider" <eschneider@xxxxxxxxxxxxx> wrote in message
news:%23FmlHbj1GHA.4648@xxxxxxxxxxxxxxxxxxxxxxx
Has anyone seen weird issues when installing custom clients on top of
version?
Seen it a few times, remove all versions an reinstall the current again
and it works fine.
This a fairly complex remoting n-tier application, was installed with a
MSI package, other clients work fine when I see the issue.
Maybe i'm missing something, or doing something wrong?
Thanks,
Schneider
.
- References:
- Install on top of old client version issues?
- From: schneider
- Re: Install on top of old client version issues?
- From: Phil Wilson
- Install on top of old client version issues?
- Prev by Date: WebSetup --System32 dll installation
- Next by Date: Questions about conversion of .Net 1.1 to 2.0
- Previous by thread: Re: Install on top of old client version issues?
- Next by thread: ClickOnce deployment question with content files (online-only mode)
- Index(es):
Relevant Pages
|