Resource.* related Intellisense does not work well when app project contains resources from multiple library project sources

[pjcollins]

Steps to Reproduce

1. Download the CustomControl.zip attachment and load up the MainActivity.cs file in VS or VS Mac.
2. Wait for initial design time resources processing to occur.

Expected Behavior

All Resource.* references from all locations can be discovered via intellisense.

Actual Behavior

VS and VS Mac now display different Resource.* intellisense results.
VS Mac indicates that it has encountered some ambiguity with some of the resources included in the primary App:

VS has issues discovering the resources included in my library project:

Version Information

d15-7 VS - https://gist.github.com/pjcollins/a372f14861bdcb94931cc0c9df8e05a8
VS Mac - https://gist.github.com/pjcollins/0d6fd2c677683fd3d8ea67ac4b38a24e

Log File

Initial design time build logs from VS for both the app and library project appear to succeed, however I have attached those binlogs:

ClassLibrary1_Debug_AnyCPU_DesignTimeBuild_2018-05-21T11_56_13.2904584-04_00.zip

[dedmen]

Have the same issue with the ambiguity. But I even get it if the resource name is unique to my project and should only exist once.
In my Resource.Designer.cs I get warnings for every member that Member with the same name is already declared which is simply not true. If I do a search through my entire project I only get that one result and the ID in my axml.

[dotnet-policy-service]

We suspect this issue is stale and no longer relevant. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.

[dotnet-policy-service]

This issue will now be closed since it had been marked "possibly-stale" but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.