Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

WiX DTF Custom Action Current Directory Different When Interop is in GAC #4458

Closed
wixbot opened this Issue Jun 27, 2014 · 4 comments

Comments

Projects
None yet
2 participants
Collaborator

wixbot commented Jun 27, 2014

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.

Originally opened by chrpai

Collaborator

wixbot commented Jun 28, 2014

Pull request - wixtoolset/wix3#96

Originally posted by rseanhall

Collaborator

wixbot commented Jun 28, 2014

Originally changed by barnson
Area set to sdk
AssignedTo set to shall
Release changed from v3.x to v3.9
Resolution set to fixed
Status changed from Untriaged to Resolved

Collaborator

wixbot commented Jun 28, 2014

Originally changed by barnson
Status changed from Resolved to Untriaged

Collaborator

wixbot commented Jul 10, 2014

Status changed from Untriaged to Resolved

@wixbot wixbot added bug sdk labels Dec 20, 2015

@wixbot wixbot added this to the v3.9 milestone Dec 20, 2015

@wixbot wixbot closed this Dec 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment