We generally use the rule that all source content needs to be separate. Daniel Ratliff
From: [email protected] [mailto:[email protected]] On Behalf Of Robert Spinelli Sent: Wednesday, January 13, 2016 12:59 PM To: [email protected] Subject: [mssms] Package vs App Model - Package Source Trying to see what others do for this, example below: If you have WinZip that is setup as a legacy package and also as an application that both use the same install (e.g. WInzip.MSI) do you let the legacy package and application use the same source or do you split it? Example same source: Legacy package: \\fileserver.contoso.com\packagesource\winzip\r1<file:///\\fileserver.contoso.com\packagesource\winzip\r1> Application : \\fileserver.contoso.com\packagesource\winzip\r1<file:///\\fileserver.contoso.com\packagesource\winzip\r1> I have always split it and used 2 separate sources but others have brought up that then the package server will need double the space. It's not a problem of space for the DP's because of single instance store. My feeling is someone is going to do something like put a file in the package source (\\fileserver.contoso.com\packagesource\winzip\r1<file:///\\fileserver.contoso.com\packagesource\winzip\r1>) for the WinZip legacy package, update the content and now hash issues are going to occur for the WinZip Application. Thanks Rob The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
