dotnet / dotnet/project-system
Changing the TargetFrameworks list for a loaded project does not always has an effect
Open
Feature-Configurations
Feature-Multi-Targeting
Triage-Approved
- Dominant language
- C#
- Stars
- 1k
- Forks
- 415
- PR merge metrics
- No merged PRs in 30d
Description
_From @jeromelaban on April 5, 2018 17:3_
In VS2017 15.7 Pre2, Win10 FCU:
* Create a Project A, with `netstandard2.0;net46`
* Create a Project B, with `netstandard2.0;net46`
* Make Project B reference project A
* Build once
* In the same VS instance, using the `Edit csproj` context menu
* Edit Project A, set `netstandard2.0`
* Save
* Edit Project B, set `netstandard2.0`
* Save
* Rebuild the solution
Sometimes, B won't compile because of a A does not target `net46`, a target that has just been removed.
Using these repro steps, you may also find that the `Edit csproj` context menu does not always open the file.
_Copied from original issue: Microsoft/msbuild#3169_
Contributor guide
Assessment
This issue has not been assessed yet.