Preventing a Patch from Requiring Access to the Original MSI - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

renaud.pelissier
Posts: 1
Joined: Fri Oct 16, 2009 3:35 pm

Preventing a Patch from Requiring Access to the Original MSI

Hello,

I am evaluating your software and I must tell, as a developper, that I am quite impressed by the quality of the job you made!

One of the main features I am interested in is the "Patch" and "AutoUpdate" system.
Here are the steps of my scenario :
  • I have a first package installing two Java services (Service1.jar, Service2.jar), let's say [myPackage.1.0.0.msi].
  • Service1.jar has changed, so I build a new package [myPackage.1.0.1.msi]
  • I build a patch [Patch.msp]
When I run the patch, that should basically do :
  • Stop Service1
  • Overwrite Service1.jar
  • Start Service1
I can not manage to prevent it from requiring the first package (but my user didn't keep it).

I spent a lot of time on the Microsoft website http://msdn.microsoft.com/en-us/library ... 85%29.aspx, but it is really too deep into the MSI details. I disabled the binary delta for the patch but it is still is asking for the package.

What do I miss, how to tell the patch not to require the previous MSI? Is there a way to check where the dependancies are?

Thanks for your help!

Best regards,

Renaud
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Preventing a Patch from Requiring Access to the Original MSI

Hi Renaud,

Thank you for your interest in Advanced Installer.

The patch needs the original MSI only if it detects that resources installed by the MSI are missing or corrupt.

A possible solution is to:
- go to the Advanced Installer installation folder
- go to the "templates" subfolder
- open the "template.pcp" file with Orca
- set the SEQUENCE_DATA_GENERATION_DISABLED property to 0 and save the changes
- rebuild the patch

This will make the patch automatically generate the patch sequencing information and the original MSI should no longer be required for the patch installation.

If the original MSI is still required, most likely the installed files are modified after they are copied on the target machine. In this case there are two options:
- provide the original MSI when prompted
- make sure that the installed files are not modified or removed

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”