Code: Select all
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<startup>
<supportedRuntime version="v2.0.50727"/>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
</configuration>
Ahhhh, that's the problem then. If AI is unpacking my attached .NET .exe using a temp name, then when the .exe is run, the .NET CLR doesn't find a matching .exe.config file name. To clarify, if my .exe is named myExe.exe, then my configuration file must be myExe.exe.config in order for the .NET CLR to use it.Eusebiu wrote: I'm not sure why your EXE custom action does not find the .config file. The file is indeed extracted in the %temp% directory, but it uses a temporary name (i.e. MSI6F1.tmp), however this should not cause any problem.
FOLLOW US
Get the latest news in Application Packaging