Skip to content
New issue

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

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't create shadow copy that already exists #147

Merged
merged 1 commit into from
Aug 28, 2020
Merged

Don't create shadow copy that already exists #147

merged 1 commit into from
Aug 28, 2020

Commits on Jul 15, 2020

  1. Don't create shadow copy that already exists 

    In some scenarios the same unmanaged DLL is resolved multiple times
(e.g. when using System.Data.SQLite.SQLiteConnection). The previous
implementation would then try to create new shadow copies of the same
DLL during subsequent resolves. This failed during copy of the DLL since
the parameter to enable overwriting was not set to true.

This fix checks if the shadow copy already exists and skips the copy
step if it does. The path to the existing shadow copy is returned
instead.

Fixes natemcmaster#146
    @KatoStoelen
    KatoStoelen committed Jul 15, 2020
    Configuration menu
    Copy the full SHA
    1c38b0c View commit details
    Browse the repository at this point in the history