Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not reference Wyam.Common namespace with nuget #1

Open
kiyo4act opened this issue Feb 19, 2020 · 3 comments
Open

Could not reference Wyam.Common namespace with nuget #1

kiyo4act opened this issue Feb 19, 2020 · 3 comments

Comments

@kiyo4act
Copy link

I started to create a new shortcode dll with Wyam.Common package following steps but my project could not solved reference under Wyam.Common namespaces. (e.g. create a new shortcode class implement IShortcode interface.)

  1. Create a new class library project in Visual Studio 2019 (TargetFramework is netstandard2.0)
  2. Open nuget package manager and install latest Wyam.Common
  3. Add "using Wyam.Common.xxx" but could not be found.

It works fine that Download Wyam.Common.nupkg and rename ext to zip, then I extract dll file and add the reference directly.

@daveaglick
Copy link
Member

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?

@daveaglick
Copy link
Member

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.

@daveaglick daveaglick transferred this issue from statiqdev/Statiq.Web Feb 29, 2020
@kiyo4act
Copy link
Author

kiyo4act commented Mar 1, 2020

Thanks for your kindly reply and information.

My situation is summarized in this VS screenshot.
Capture

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants