升级 .NET 版本后，TwoWay 或 OneWayToSource 绑定无法在只读属性上工作

Question

I have WPF application with target framework version as 4.5 . Now I have switched to version 4.6.2 .

After that, I am getting the following error in multiple places.

A TwoWay or OneWayToSource binding cannot work on the read-only property 

I am using Visual Studio 2017 .

Call the project as A and it has B, C, D as dependencies . While B, C, and D are attached as DLL 's I am getting the error. If they are attached as projects I am not getting the error.

Note: All B, C, D are 4.5 version projects and I am not changing them into 4.6.2 for running this project.

Can anyone update me on how to proceed further here and if there is any mistake in the way of approaching?

Update 1:

The related question is different from my case:

A TwoWay or OneWayToSource binding cannot work on the read-only property

Update 2:

The following question is similar.

A TwoWay or OneWayToSource binding cannot work on the read-only property .

but the link provided in the answer seems to be broken or redirected:

https://connect.microsoft.com/VisualStudio/feedback/details/773682/wpf-property-with-private-setter-is-updated-by-a-twoway-binding

Answer 1

I know it's year late, but if anyone runs into this, it's known problem. After framework upgrade, parts of my UI started throwing InvalidOperationException. The fix was easy, just add explicit Mode=OneWay to the binding. But I still needed to know why it started if nobody changed anything in code for quite some time.

I found the solution here: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/retargeting/4.5-4.6.1#two-way-data-binding-to-a-property-with-a-non-public-setter-is-not-supported

Attempting to data bind to a property without a public setter has never been a supported scenario. Beginning in the .NET Framework 4.5.1, this scenario will throw an InvalidOperationException. Note that this new exception will only be thrown for apps that specifically target the .NET Framework 4.5.1. If an app targets the .NET Framework 4.5, the call will be allowed. If the app does not target a particular .NET Framework version, the binding will be treated as one-way.

The problem was always there, it only just started throwing exception when it happens.