When referencing dll compiled with .net standard 2, intellisense in vs code stop working.

[gabomgp]

I create a minimal test case.

The problem is in intellisense is not working when i reference a dll copiled with .net standard 2.0

The code is avalaible in https://github.com/gabomgp/test-case-bug-bakery

In the code linked, the build.cake is inside a folder with a project in .net standard 2.0. But, the problem is showed too when the build.cake is outside that folder, and inside the solution's folder, where there are other projects, some projects compiled with .net standard 2.0 and others with .net 4.6.

[gabomgp]

I think, this issue is related to OmniSharp/omnisharp-roslyn#996

But the solution in that issue dosn't works in .cake files. The solution is:

#! "netcoreapp2.0" directive at the top of your script to force the assembly resolution to assume .NET Core 2.0 mode.

[jnm2]

I'm getting the same thing, but with a normal .NET Framework assembly. Nothing .NET Core in the picture.
Just add #r System.IO.Compression.FileSystem and OmniSharp fails. @mholo65 should I start a new issue for this or is it connected? In addition, OmniSharp is incorrectly marking ZipFile as not found without that #r line even though Cake runs it fine without any #r.

[bjorkstromm]

@jnm2 ah, I see.. Don't think we actually handle #r directives correctly in Bakery. In Cake itself it's easier, since we use reflection and that will automatically load assemblies from GAC based on only assemblyname. With this bakery/omnisharp-thingy we expect paths to DLLs.... @patriksvensson any ideas?

[jnm2]

I ran into the same problem today with #r System.Net.Http.

[bjorkstromm]

@jnm2 I created a separate issue for GAC loading here #85

@gabomgp about netstandard2.0, that's not even supported in Cake itself. Why would like it to be supported via intellisense? netstandard2.0 will work eventually, but that will take a little more effort.

[bjorkstromm]

@gabomgp said:

But the solution in that issue dosn't works in .cake files. The solution is:

#! "netcoreapp2.0" directive at the top of your script to force the assembly resolution to assume .NET Core 2.0 mode.

Yes, we don't currently support that directive in Cake.

[jnm2]

@mholo65 The bigger issue is that I didn't need the #r line for Cake's sake, only OmniSharp's sake. Is there an issue tracking keeping OmniSharp in sync with Cake's default assembly references?

[bjorkstromm]

@jnm2 oh, totally missed that. No there's no issue for that. Would you mind submitting one.

[jnm2]

Sure. #86

[gabomgp]

@mholo65 The reason is that i want to regenerate the whole database and populate that using entity framework core and cake as the task runner. But, the models and the context are projects compiled with .net standard 2. I must use the context and models to use code first migrations with entity framework core, to create the empty database and populate it easily in developer's machines. I can't do it from cake because the code is in a .net standard 2 library. So, that's the reason :)

[patriksvensson]

@gabomgp I'm sorry but I don't understand this. Cake does not support netstandard2.0 in any way, so why would it help to have support for it in Bakery? You simply can't reference a netstandard2.0 assembly in a cake script until we've merged the work done in Cake for supporting it.

Would you mind elaborating on why you would need Bakery support for this when it's not supported by the Cake script runner?

[bjorkstromm]

@gabomgp wouldn’t it make more sense to use the .NET Core EF Command Line Tools for dropping and creating your database? You can still use Cake as task runner and no need to reference DBContext in your Cake script.

[gabomgp]

@mholo65 It's a good alternative. Thanks for the suggestion. I'll try it.

[ecampidoglio]

I'm running into this issue with VS Code on macOS:

Oddly enough, the Intellisense itself is working. Also, there are no errors in the Omnisharp log and the only symbol where I'm getting this error on is the Task alias.

@mholo65 Do you have any suggestions on how to resolve this?

[bjorkstromm]

@ecampidoglio hmm, seems like some reference is not passed correctly to Roslyn. What version of Cake are you using? Are you using Cake, Cake.CoreCLR or Cake.Tool? What version of Cake.Bakery are you using? What version of C# for VS Code are you using? Do you use the default OmniSharp version shipped with the VS Code extension, or do specify another version? Do you have a minimal script where this can be reproduced?