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

Fixed: WPF workaround for importing extensions does not always work #201

Merged
merged 2 commits into from Jul 24, 2020
Merged

Fixed: WPF workaround for importing extensions does not always work #201

merged 2 commits into from Jul 24, 2020

Commits on May 13, 2020

  1. Fixed: WPF workaround for importing extensions does not always work 

    The issue happens when BaseIntermediateOutputPath is overridden, thus
MSBuildProjectExtensionsPath gets assigned without generated suffix
even in *_wpftmp.*proj file.
Since _SdkOriginalProjectExtensionsPath didn't have a fallback value -
that prevented importing project extensions. This change adds the
fallback, making it effectively like "if there's a suffix - remove it,
otherwise use as is".
    @ivan-danilov
    ivan-danilov committed May 13, 2020
    Configuration menu
    Copy the full SHA
    c37a5b9 View commit details
    Browse the repository at this point in the history

Commits on Jun 3, 2020

  1. Merge branch 'master' into fix-wpf-workaround

    @ivan-danilov
    ivan-danilov committed Jun 3, 2020
    Configuration menu
    Copy the full SHA
    7cb4761 View commit details
    Browse the repository at this point in the history