G
Guest
Hi,
we see some strange behavior with the latest version of our deployment package
Background
We have a .Net product that is deployed via a website. Developed with VS.Net 2003, the deployment project uses a "Web bootstrapper" and has a valid signature
On the download site we have to files
- the product.ms
- the Setup.Exe (encoded with the url to the product.msi file)
A user downloads the product by clicking a link on the website that points to the Setup.Exe file and running (or saving and then running) the Setup.Exe file
The first time the user activates the Setup.Exe file - he get's an error "Setup was unable to find msi package or patch 'http://complete.url.com/to/download/product.msi'";
The second time the user runs Setup.Exe the product.msi filess is downloaded and the installatione runs fine
After that the download works fine. The error can be reproduced by deleting the temporary internet files
This error is something that has started recently (within the last month). It seems that the Setup.Exe simply times out to quickly.
Does anyone know if there is a way to get around this problem
Thanks for any help
B
Mad
we see some strange behavior with the latest version of our deployment package
Background
We have a .Net product that is deployed via a website. Developed with VS.Net 2003, the deployment project uses a "Web bootstrapper" and has a valid signature
On the download site we have to files
- the product.ms
- the Setup.Exe (encoded with the url to the product.msi file)
A user downloads the product by clicking a link on the website that points to the Setup.Exe file and running (or saving and then running) the Setup.Exe file
The first time the user activates the Setup.Exe file - he get's an error "Setup was unable to find msi package or patch 'http://complete.url.com/to/download/product.msi'";
The second time the user runs Setup.Exe the product.msi filess is downloaded and the installatione runs fine
After that the download works fine. The error can be reproduced by deleting the temporary internet files
This error is something that has started recently (within the last month). It seems that the Setup.Exe simply times out to quickly.
Does anyone know if there is a way to get around this problem
Thanks for any help
B
Mad