Thanks for clicking,

I have this application right, and its really close to being finished. It will be used by lots of people accross the state and so i've decided to use ClickOnce for deployment. Is there any way to change the default install directory for a clickOnce application other than the unique cache directory it creates for itself? I need to install this on the root of a USB Flash drive so the application can be used on different machines by the same person.

I've been using ClickOnce to distribute apps within our corporate network for quite a while and I do not think the default install directory can be modified.

If your application does not require any files other than those that reside in the bin\release directory then try copying the necessary files directly to the flash drive (bypassing the deployment altogether). Depending on the complexity of your application it may work just fine. If your ClickOnce includes the .NET Framework and other required components than this option most likely will not work.



Best Regards,
Earl Francis

Thanks ef1196. Copying the files to the flash drive manually would pretty much defeat the purpose of trying to use clickonce deployment for this application because of this particular scenario (installing it on a flash drive). i need to have this all automated. I was also thinking that if ClickOnce did not fit my needs i would just write a VBScript and have that run on the client machine to perform the initial install on the flash drive.

The complexity of the application is quite high because the .NET application has to call a VB6 app written by another to complete certain functionality, and im relying on reg free COM to make this work. It almost seems like i have to write a seperate install program to install everything, but im trying to do as much research as i can in order to make the best decision.

What about editing the right Manifest file?