0

In a test project I created a core project with a test class .

I configured the project in the project.json to compile as core and dnx like this:

{
  "version": "1.0.0-*",

  "dependencies": {
    "NETStandard.Library": "1.6.0"
  },

  "frameworks": {
    "netstandard1.6": {
      "imports": "dnxcore50"
    },
    "dnx46": {
      "imports": "dnx46"
    } 

  }
}

now i create a .net 4.6.2 console project and add manually reference to the output form this folder bin\Debug\dnx46

now when i instantiate the class and call a method on it it works. It gets compiled and the runtime returns the currect result.

But the IDE seems to not resolve the types for intellisense

am I doing something wrong?enter image description here

What am I missing?

This can also be found at this issue: https://github.com/aspnet/Tooling/issues/875

Boas Enkler
  • 12,264
  • 16
  • 69
  • 143
  • Probably it's the same as in here: http://stackoverflow.com/q/40709226/5311735 – Evk Nov 22 '16 at 07:29
  • no it isn't in my case the project is compiled successfully and is running. – Boas Enkler Nov 22 '16 at 07:31
  • In that case it is too, if you read the answer (OP was thinking that it's not, but it is - just like in your case). – Evk Nov 22 '16 at 07:32
  • All in all, you can try to browse .net core tooling issues: https://github.com/aspnet/Tooling/issues. There are many of them related to intellisense, maybe you will find your concrete situation there. That situation is clearly a bug, and it's not an uncommon one. – Evk Nov 22 '16 at 07:38
  • I don't believe this as I don't reference the projecti na solution., I reference the assembly from the output, so there aren't multiple projects in it – Boas Enkler Nov 22 '16 at 07:38
  • Yes you are right, that's a bit different bug, missed that you reference directly. – Evk Nov 22 '16 at 07:39
  • i'll open a ticket there maybe the issues are at least linked. – Boas Enkler Nov 22 '16 at 07:41
  • Compared to VSCode which updates more often to catch up with the changes, I believe VS might give you more issues than you imagine. Except reporting to Microsoft and hope they can fix, I don't think posting on SO can lead to any solution. It is simply a Roslyn related bug on .NET Core support. – Lex Li Nov 22 '16 at 13:44

0 Answers0