We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

mstarnaud
Posts: 45
Joined: Mon Apr 15, 2013 9:44 pm

Accessing files without deploying them?

Hi

We have a scenario where we would like the setup to include a file, but we don't want to deploy it on the customer's computer. Usually we would use temporary files, but even those get taken out of the setup and placed in the user's temp folder (see http://www.advancedinstaller.com/forums ... =5&t=25943). Even if they are destroyed afterwards, that's not what we want : for some time the user can access them freely. The best way I can explain it is that it should be an "internal resource". And we want to be able to access it in an InstallerClass called in a custom action.

How can we accomplish this?
Eusebiu
Posts: 4971
Joined: Wed Nov 14, 2012 2:04 pm

Re: Accessing files without deploying them?

Hi,
We have a scenario where we would like the setup to include a file, but we don't want to deploy it on the customer's computer.
You can achieve this by using the "Launch attached file" custom action which will embed the file in the MSI package, but will not install it on the user's machine.
And we want to be able to access it in an InstallerClass called in a custom action.
Unfortunately, the ".NET Installer Class" custom action cannot use an attached file (file embedded in the MSI package) or a temporary file (added using the "Temporary Files" toolbar button from the Files and Folders page) because of some limitations.

Best regards,
Eusebiu
Eusebiu Aria - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”