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

Closed
savornicesei opened this issue Jun 3, 2021 · 4 comments
Closed

Could not reference Wyam.Common namespace with nuget #1

savornicesei opened this issue Jun 3, 2021 · 4 comments
Labels
devops Build process or infrastructure changes
Milestone

Comments

@savornicesei
Copy link
Contributor

savornicesei commented Jun 3, 2021

Issue by 18konoe
Wednesday Feb 19, 2020 at 10:53 GMT
Originally opened as Wyamio/Wyam#1


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.

AB#12

@savornicesei
Copy link
Contributor Author

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?

@savornicesei
Copy link
Contributor Author

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.

@savornicesei
Copy link
Contributor Author

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.
Capture

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

@savornicesei savornicesei added the devops Build process or infrastructure changes label Jun 20, 2021
@savornicesei savornicesei added this to the v3.0.0 milestone Jun 24, 2021
@savornicesei
Copy link
Contributor Author

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Build process or infrastructure changes
Projects
None yet
Development

No branches or pull requests

1 participant