C# Custom Action - Where its files come from - Advanced Installer Community

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!

invalidptr
Posts: 79
Joined: Thu Nov 18, 2010 7:10 pm

C# Custom Action - Where its files come from

I've created a custom action in a C# dll. I've had success with it in the past but I've run into a road block. Looking in the logs I see it's executing from here C:\WINDOWS\Installer\MSI71.tmp- and not C:\Documents and Settings\Administrator\Local Settings\Temp like I would expect.

I just specified a single DLL but MSI71.tmp- contains other files that are needed. A happy coincidence? Can this be controlled?

What mechanism is used to determine what files go in here? Unfortunately all the files in MSI71.tmp- have the current date and time and not the time they were built so tracking down the source has been difficult.

I would prefer everything were in the windows temp directory. I have multiple installers and want to control which DLL's get accessed. I'm doing that changing the temporary file's property condition to install/not installed based on the larger project.
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: C# Custom Action - Where its files come from

Hello,
I just specified a single DLL but MSI71.tmp- contains other files that are needed. A happy coincidence? Can this be controlled? What mechanism is used to determine what files go in here?
Unfortunately this process is handled internally by Windows Installer process and cannot be controlled. This location is used by Windows Installer to cache all .MSI's.
You can try to use an Attached Custom Action instead and see if it helps.

If you haven't seen it already, here is an article you may find helpful.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
invalidptr
Posts: 79
Joined: Thu Nov 18, 2010 7:10 pm

Re: C# Custom Action - Where its files come from

Thanks Mihai for the link to the article. That's how I got started with all this in the first place.

To those that happen upon this thread, here's some more insight into my original post. When you specify the Wix.CA.DLL in your custom action, when the installer is built, most of the files along side Wix.CA.DLL will get bundled together. Then during install, the contents will get unzipped (in my example into C:\WINDOWS\Installer\MSI71.tmp-) into it's own sandbox and execute from there. I added a .config file to the project and ultimately into the directory but it didn't get included for some reason. I did the same with a DLL and it did get packaged up. YMMV
kirankunnam
Posts: 10
Joined: Thu Sep 29, 2011 5:50 am

Re: C# Custom Action - Where its files come from

for C# customer action function how to i get the values that are enter in installation time.
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: C# Custom Action - Where its files come from

Hi,
kirankunnam wrote:for C# customer action function how to i get the values that are enter in installation time.
Can you please give me more details? How are you configuring your custom action? Are you using an installer class action?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”