Frequently Asked Questions, Application Packaging

Q:
Gert asks: When using SVS, it is possible that a file being replaced by a Windows security update might actually exist in more than one place -- in the base and also in one or more application layer. What happens? How do I ensure that the machine gets updated correctly?

Q:
Terry wrote: "I am responding to a message you had posted on Juice about an SVS package interaction with SharePoint. We came across
another similar problem of a base program that needs to detect a program in an SVS layer in order to work right. Can you point me in the right direction of how to overcome this problem?"

Q:
Conor asked, "Here's the deal, I created a layer (using WPS 7.0 beta) that inserts several icons into my personal start menu during installation. So I went into advanced layer properties and removed the icons out of my SID area (they still exist in the read-only section) and export the layer to .VSA. If another user imports that layer, and activates it, they get the icons in their start menu, but I don't until I reset the layer after activation. Should I remove all user specific information out of the read-write layer before I export the VSA?"

Q:
Jim asked, "I'm currently using Wise Package Studio to package my applications. Will I still need this after I adopt SVS?"

Q:
Sara asked, "Do I need to create different Virtual Software Packages for each operating system that the package will be deployed to?"