Join GitHub today
WiX DTF Custom Action Current Directory Different When Interop is in GAC #4458
I had a previous bug regarding an MSBuild compile problem when the Microsoft.Deployment.WindowsInstaller assembly is in the GAC. Today I noticed another problem. If the assembly is not in the GAC, DTF sets the CurrentDirectory to the TEMP directory that sfxa extracts the resources to. However, if the assembly is in the GAC, the current directory gets set to the GAC path that contains the assembly. This behavior change breaks code that uses relative paths to access extracted resources. A work around is to use reflection to work out the location of the executing assembly and change the current directory to this location. I would think the intent was for the current directory to be the same without influence of the assembly being in the GAC or not.