Re: Setup Project

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hi Alex,

Appreciate your update and response.

The problem is caused by file version. By default, windows installer will
reinstall if the file is missing or is an older version. Otherwise it will
keep the original file.

From your reply, I have seen that this issue only happens in beta testing.
Since file version checking is by windows installer design. Would you like
to use a workaround to solve this problem? The quickest solution you can do
is create a bat file and type "msiexec /I <Setup MSI file path>
REINSTALLMODE=amus". Then run the bat file instead of directly run the msi
file. By changing REINSTALLMODE option, the installer will override the
existing files without checking its versions. For the detailed information,
please visit http://msdn.microsoft.com/en-us/library/aa371182(VS.85).aspx.

For your debugging problem, I cannot reproduce it. What I did is:
1. In setup project, custom actions tab, right click Install folder, and
click "Add Custom Action".
2. Double click Application Folder, and click "Add Assembly" on the right
side.
3. On the select component dialog, click Browse tab and choose the exe file
from file system with pdb file in the same folder. And click Ok.
4. In the exe file project, find the entry point (generally it is "Main"
function) of the application, add "System.Diagnostics.Debugger.Break();"
at the first line of the function.
5. Build the exe project, because setup project will not automatically
build custom action referenced project.
6. Rebuild the Setup project.
7. Run the setup application.
Please try it again, and make sure that the dll you want to debug has
related pdb file. If you want to debug external dll or exe, you must have
the symbol files on your machine.

Please let me know if the quick solution works for you, or you need any
other help.

Regards,
Hongye Sun (hongyes@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • Re: Error! Unable to check for updates on this computer
    ... able to get updates to not being able to reinstall Office ... the Msicu.exe utility or the Msicuu.exe (Windows Installer ... >detection process is at about 57% my HD access is ... >control can load ...
    (microsoft.public.officeupdate)
  • Re: Windows installer problem
    ... I get the package ... Windows Installer, then "This patch package could not be opened. ... Tried to delete office and reinstall ...
    (microsoft.public.windowsxp.general)
  • Re: PC repaired,lost disc- need complete reinstall of MOSE2003
    ... I would suggest taking your computer back to the tech who reinstalled Office and tell them to fix it right this time. ... Then Windows Installer popups saying it is trying to install ... the original disc which is lost over a year. ... I deleted 2007 trial but then 2003 keeps trying to reinstall ...
    (microsoft.public.office.misc)
  • Re: Microsoft Office Home Edition 2003
    ... You receive an error message you try to repair, reinstall, or install an "on ... Windows Installer: This patch package could not be opened. ...
    (microsoft.public.office.misc)
  • Re: Cant update Office 2000 pro
    ... I used that 'cleaner' again and had to reinstall the office from scratch. ... the SR-1a upgrade I am prompted with a message that the SR-1a is already ... > This will clean out the confused Windows Installer data so you can ... >> Windows XP Home Edition upgrade version. ...
    (microsoft.public.officeupdate)