Skip to content
This repository has been archived by the owner on Aug 8, 2024. It is now read-only.

Fix TargetFrameworkRootPathFallback when MSBuild API is used in different process #22

Merged
merged 1 commit into from
Jul 22, 2017
Merged

Fix TargetFrameworkRootPathFallback when MSBuild API is used in different process #22

merged 1 commit into from
Jul 22, 2017

Commits on Jul 22, 2017

  1. Fix TargetFrameworkRootPathFallback when MSBuild API is used in diffe… 

    …rent process

When reading the TargetFrameworkRootPathFallback from the app.config, we need use the configuration file from the current MSBuild Exe Path rather than the one from the current process. This is consistent with the behavior of `ToolsetConfigurationReaderHelpers.ConfigurationFileMayHaveToolsets()`.
    @DustinCampbell
    DustinCampbell committed Jul 22, 2017
    Configuration menu
    Copy the full SHA
    aae233a View commit details
    Browse the repository at this point in the history