>>>>A compromise I've used in the past is to create a root folder called something like "NetShare", and make sure that all shared apps/data are installed to one or more subfolders of that (e.g. \NetShare\MyApp). That way you have a distinct separation between programs and data that are for local execution only, and those that may be executed locally or by other machines on the network. It can also simplify tasks such as backup.
>>>
>>>That only makes sense when you have some control over the networks. In this case, it's a vertical market app, so all I can control is this application.
>>
>>Having a \NetShare folder makes exactly the same sense as having a \Program Files folder. If you can install your app to \MyApp there's no reason you can't install to \NetShare\MyApp.
>>
>
>Guess I wasn't clear about what I meant. Since it's a vertical, while I can install to such a folder, I have no control over where other networked apps are installed. So this app can certainly recommend such a structure, but it's not like an in-house situation where IT can enforce such a structure.

That's what I was getting at. Whenever I've installed my own, or third-party M/U apps, the server admin has either already created something like \NetShare or has thought it a good idea once I suggested it to them.