I asked the same question in a completely different zone, but didnt receive an answer. The programming zone is probably more suitable for this type of question.
My question is this: Is developing a software, which is to be run directly from a network drive, any different than developing a software who runs from the local harddrive? (except the obvious that working from a network drive might possibly make it run much slower)
And the reason I want to know this is because my company distributes alot of different applications which are to be installed locally on computers. But we frequently get the question whether these software can be run directly from a network drive instead. Most of the applications, come with very poor documentation so I thought I might try to experiment a bit with this myself.
What I had in mind was that I could perhaps modify the .msi packets. Making sure that the necessery registry entries for the software are installed on the local computer, and then that the programfolder/files are installed on a network drive.
However, the program I have been experimenting on doesnt seem to work this way. But the curios thing is that I can copy the program folder to a second internal harddrive on the local computer (E:) and run it from there without any problems. So in what lies the technical difference between running the application from a network and a local HDD? I have been trying to use "process monitor" to observe excactly what the difference is, but I cant see any obvious error messages - but perhaps I just dont know what to look for...?
So...is there anything in general that I can do to make software executable from a network drive - by for example modifying the msi-packet?