Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

16
  • Can you provide exact steps to reproduce (how to set up the projects, etc.)? Commented Apr 16, 2018 at 7:43
  • Do you have to add it as a reference like that, rather than as either a package or a project reference? I can't say I've seen any "old-style" references like that (with hint paths) in "new-style" .NET Core projects. Commented Apr 16, 2018 at 7:46
  • Should work fine. I'd say in current state problem is not reproducable (at least for me). Commented Apr 16, 2018 at 7:54
  • @Daisy You have to add a reference to a DLL instead of a project. Commented Apr 16, 2018 at 8:01
  • 1
    I guess if you have to do it that way, you have to. (I'd still encourage you to try to move away from that over time.) Like Evk, I can't reproduce this - I've just tried doing it with Json.NET as a DLL reference, and it was fine. When you build the project, do you get the DLL in the output directory, e.g. in bin/debug/netcoreapp2.0? Commented Apr 16, 2018 at 8:27