Hey guys ...
I have created a setup package for a VB app using the Package and Deployment Wizard. The application was created as an EXE and the .CAB file that was created by the PDW packaged around 7 DLLs to go with the EXE.
Here's my problem - is there any way that I can run the setup package on a shared drive and install the DLLs on this shared drive instead of putting it on the client machines ? The application and the DLLs will reside on this server, but the application itself will be run from the client machine.
I do not want to overwrite any existing DLLs on the client machine. Has anyone encountered this problem before ? Is this really feasible ?
Any help will be appreciated. Thanks,
- Subha Nothing is impossible, even the word impossible says I'm possible.
I have created a setup package for a VB app using the Package and Deployment Wizard. The application was created as an EXE and the .CAB file that was created by the PDW packaged around 7 DLLs to go with the EXE.
Here's my problem - is there any way that I can run the setup package on a shared drive and install the DLLs on this shared drive instead of putting it on the client machines ? The application and the DLLs will reside on this server, but the application itself will be run from the client machine.
I do not want to overwrite any existing DLLs on the client machine. Has anyone encountered this problem before ? Is this really feasible ?
Any help will be appreciated. Thanks,
- Subha Nothing is impossible, even the word impossible says I'm possible.