Slept at 2 AM and woke up at 4 AM to check the notifications on my mobile and I saw this post. The team members are probably asleep now. The irony being today the team had planned to complete the migration to .NET Standard
I am honestly glad that you've made the post and reported the issue on time. Because a lot of organizations have dived in and have based their IPs on our frameworks this report is priority 1
In addition to the solution link you've provided, due to the project planning and management structure here, I have spent hours already looking to find the minimal amount of changes the team would have to make in the shortest interval of time to the current project repositories to address this. I had a strange hunch of hitting something down the line when the team mentioned that .NET Standard 1.0 was a total replacement for PCL Profile 259
and it would save a lot of project management time if we just switched to .NET Standard
Being the Lead, I am taking the liberty of officially postponing the .NET Standard migration date to 26th of May
In the meantime, as I am traveling, I shall ask the team to revert back the NuGet packages by deleting the previously published NuGet packages which should essentially force referencing of PCL Profile based libraries.