If you install the MSP using the PATCH property, you simply call msiexec from within a batch file and use the %~dp0 batch file parameter to fully-qualify the msp path (assuming you've put the msp in the same location as the msi along with the batch file also).

For installing it after the fact and detection, you'll probably need to write a script and query the Windows Installer DB using the WindowsInstaller.Installer COM object: http://support.microsoft.com/kb/974653, http://msdn.microsoft.com/en-us/library/windows/desktop/aa369432%28v=vs.85%29.aspx

I am currently looking to migrate from using packages to using applications.

If I have an MSI that I am deploying as an application - what is the best way to deploy an MSP patch for it?

If I go down the route of creating a manual deployment type and installing the MSP from a script then I have to add a detection clause which I'm not sure how to setup in terms of what files the MSP would add.

I read another thread on specifying the MSP as part of the MSI install but wasn't sure on that either as the patch paramter requires the full path?

Any guidance please?

Jay

Thanks Jason.

I was planning to install the MSI as an MSI Deployment Type so that the product codes and detection clause are all done automatically. There is no way I can specify the MSP within this method is there?

Therefore am I best deploying the whole install from within a script and specifying the PATCH property?

Yes, my first paragraph above describes that. Simply use a batch file to wrap the msi. You can start out in the app creation wizard by specifying the MSI so it will automatically create the detection and then later go back and change the install command-line to reference the batch file or you can simply manually create the detection which allows you to browse to the MSI. No real difference and both end up in the same place. I would probably choose the first.

Thanks Jason.