Could not reference Wyam.Common namespace with nuget about wyam HOT 4 CLOSED

Comment by daveaglick
Saturday Feb 29, 2020 at 20:51 GMT

Wyam.Common also targets netstandard2.0 so as far as I know it should work. This is the first report I've seen of a package install succeeding but the namespaces being unavailable. Do you see it in the list of NuGet references (and does it have a little yellow caution symbol)? What about if you try to reference a type in Wyam.Common using a fully-qualified name instead of by bringing the namespace in scope? Does that build, and if not what build error do you get?

from wyam.

Comment by daveaglick
Saturday Feb 29, 2020 at 20:52 GMT

FYI - the original Wyam project is being moved to statiqdev to continue work there as Statiq Web (the successor to Wyam and the Wyam blog recipe). Since this issue relates specifically to Wyam, I've moved it to a new replacement project for legacy Wyam issues.

from wyam.

Comment by 18konoe
Sunday Mar 01, 2020 at 03:29 GMT

Thanks for your kindly reply and information.

My situation is summarized in this VS screenshot.

Please consider to include in the test automation when your project will face the same issue.

from wyam.

@18konoe
I know this comes a year too late but this has been fixed in Wyam2 (Wyam fork to continue the project).
If you're still interested you can try out the nightly build packages hosted on GitHub.

Best,
Simo

from wyam.