Skip to content

Will VCRT forwarders always point to DLLs included in working directory for Unpackaged Win32 applications? #39

@taenri

Description

@taenri

Our team's product is an unpackaged Win32 desktop application that already includes the necessary VCRT DLLs in the EXE's local installation directory, so that we do not have to rely on users already having the corresponding VC++ Redistributable Package installed on their machine.

We are introducing a dependency that requires the use of VCRT forwarders, and we are wondering: Is it guaranteed that these forwarders will try pointing to the VCRT DLLs already included in our application's working directory first before searching for other locations? We are concerned about cases where these forwarders might throw an error if they cannot find the DLLs from a Redistributable package despite the fact that we already include them with our own application's installation.

In our working prototype, it seems that the forwarders always point to our own DLLs (based on the DLL list provided by Process Explorer), which is the desired behavior for our use case. But I wanted to ask here to get an expert opinion on whether or not this behavior 100% reliable.

Any clarification or insight you all can offer would be greatly appreciated. Cheers!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions