You must not resistribute msiexec.exe ! It's part of the operating system,
and the fact that it didn't overwrite it might have saved you from a
disaster. That's what Windows File Protection is for.
A MS support guy called Felix Wang posted this a while back. See if it
helps:
> 1. Create a shortcut to the msiexec.exe on your local machine. Change
> the target to the following:
[quoted text clipped - 10 lines]
>
> 4. In VS.Net Setup project, change the .TXT file extension back to .LNK.

Signature
Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280
> Hi All,
>
[quoted text clipped - 17 lines]
>
> Thanks in Advance
Amit - 25 Jan 2005 07:35 GMT
Hi,
Thanks for your suggestion.
I hope this will work for me.
Another things is that,to detect previous version of installed setup in of
Visual Studio VB.Net Setup and show cutom dialog for user intraction.User
will have two options for that one is Repair previous one or Remove and
Upgrade old one with new one.
Should i need to add custom action for this.Right now i have checked
checkpreviousversion property to true,it just remove the previous
version,but didn't installed new version after removing previous one.I need
to run new setup again for that.
Thanking You,
Amit
> You must not resistribute msiexec.exe ! It's part of the operating system,
> and the fact that it didn't overwrite it might have saved you from a
[quoted text clipped - 39 lines]
> >
> > Thanks in Advance