I had a very similar problem when trying to use PresentationFramework.Classic
. I got the same warning even after triple checking all the assembly details were correct (which were copy/pasted from dotPeek anyway).
However, it seems that this warning may be spurious because the compiled application works just fine. I was testing on a "clean" virtual machine image where I am confident that nothing has polluted the environment e.g. an unwanted local copy of PresentationFramework.Classic.dll
is not in the application folder.
Also, as noted by @Maverik in a comment:
I truly think this is a designer analysis limitation and you can
ignore this particular warning as long as it actually works fine.
which seems to be the same conclusion.
https://stackoverflow.com/a/8185946/3195477