Fsharp: [.NET Core SDK projects] 15.3 preview 3: dependencies are not loaded in VS

[forki]

The following solution builds fine in ionide and from command line but VS 15.3 preview 3 complains.

Repro steps

• clone https://github.com/fable-compiler/fable-suave-scaffold
• Open ClientServer.sln
• Go to Client project Utils.fs

Expected behavior

Showing no errors

Actual behavior

VS reports missing Fable links

[forki]

/cc @davkean I remember that we checked that for C# together,

[isaacabraham]

Is this paket support being broken or something else?

[forki]

paket works fine from cmd line and in ionide

[forki]

btw: the Solution Explorer shows the deps correctly:

[forki]

Ok this is only a problem with F#. I create one C# and one F# solution with dotnet new and run paket convert-from-nuget on it. I then added Newtosoft.Json as dependency to both projects:

fsharp.zip
csharp.zip

In the C# project intellisense will show Newtonsoft namespace (takes a moment for background restore but then VS knows about it). In F# project it will not.

[forki]

Even if you just dotnet new console -lang f# and add the PackageReference without Paket it does not work. fsharp-nuget.zip

[Pilchie]

I think the general problem here is that the F# language service doesn't get the commandline arguments yet :-/, even though the project system and build do have them.

We're working on this for preview 4. (@brettfo is hoping to look at it this week I think).

[forki]

Is this something that could be fixed here?

[Pilchie]

Even though I've had it explained to me 2 or 3 times now, I forget the exact details of what needs to happen here :-/

@srivatsn or @brettfo can you elaborate?

[forki]

I mean in the blog announcement we read F# support works so we were very
optimistic

Am 27.06.2017 6:30 nachm. schrieb "Kevin Pilch" [e-mail]:

Even though I've had it explained to me 2 or 3 times now, I forget the
exact details of what needs to happen here :-/

@srivatsn https://github.com/srivatsn or @brettfo
https://github.com/brettfo can you elaborate?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/3266#issuecomment-311412642,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNIZx6icKngjzEopoNDgOJRvzGymLks5sIS4ggaJpZM4OGfTF
.

[enricosada]

yes, please @Pilchie ask to remove it from blog (cc @cartermp ) at least is not another disappoinment for F# ppl (and is annoying download a preview 5GB an nothings works)
atm neither sdk 1.0 style (fsharp.net.sdk) neither 2.0 (without) works

[cartermp]

Which blog? Neither the .NET nor VS blogs have announced a release saying that F# support works. There are release notes which can be edited here, but that's the only thing I'm aware of.

[forki]

"F# Support: You can use the .NET CLI to create .NET Core console
applications and .NET Core /.NET Standard class libraries in F#. These
projects will load in this preview release of Visual Studio. We are still
working on templates to enable you to create these same projects from
within the IDE"

Am 27.06.2017 6:42 nachm. schrieb "Phillip Carter" <[email protected]

:

Which blog? Neither the .NET nor VS blogs have announced a release saying
that F# support works. There are release notes which can be edited here
https://www.visualstudio.com/en-us/news/releasenotes/vs2017-Preview-relnotes#dotnetcoreimprovements15P3,
but that's the only thing I'm aware of.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/3266#issuecomment-311416037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNNsdh4EwE0z7OQjJHl3cCRkZl6PMks5sITERgaJpZM4OGfTF
.

[enricosada]

anyway, language service and command line args bug aside, the new roslyn project system is really lightning fast (love i can edit any imported msbuild file, not just project, and it will instantly reload)

[cartermp]

I made the request to remove that bullet point completely from the release notes.

Just to clarify, the release notes are the only thing mentioning this. There are no blog posts or announcements for F# support here, nor will there be any going on until the multiple things we have in-flight are all merged in their respective branches.

For now, there are ways to be unblocked if you use nightly releases of the .NET CLI. Unfortunately, the entire process is horribly confusing right now because of different pieces across different products across different branches of those products being shipped into different previews.

[Pilchie]

For now, there are ways to be unblocked if you use nightly releases of the .NET CLI. Unfortunately, the entire process is horribly confusing right now because of different pieces across different products across different branches of those products being shipped into different previews.

BUT We're going to work today on getting something documenting what you need to pull from where to get this working, right @cartermp ? 😉

[cartermp]

Yup. I'll get instructions out as a part of an announcement on this repo w.r.t .NET Core support in VS.

[cartermp]

This is likely the same root cause as #3260, but surfacing as a different issue.

[bardeik]

Any idea on when this issue will be closed?
Anoying to get false errors in VS

[cartermp]

@bardeh This is for .NET Core SDK-based projects. #3425 is what should address this, though it's not complete.

[cartermp]

This is now fixed in #3564. (note that square is defined in another file).

[forki]

Is this already available in some form? Nightlies? Selfbuilt?

Am 12.09.2017 04:55 schrieb "Phillip Carter" [e-mail]:

This is now fixed in #3564
https://github.com/Microsoft/visualfsharp/pull/3564.

[image: all-worky]
https://user-images.githubusercontent.com/6309070/30306077-1d1e1306-972b-11e7-99a6-db793674e160.PNG

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/3266#issuecomment-328718631,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNG45ncMH_pbx2mmuO3PanEKFMX3Lks5shfKbgaJpZM4OGfTF
.

[davkean]

The CPS bits don't live in a public build yet, so no.

[forki]

Yeah. That's what I feared.
Please let me know when I can test something. We have many many things to
try out...

Am 12.09.2017 09:09 schrieb "David Kean" [e-mail]:

The CPS bits don't live in a public build yet.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/3266#issuecomment-328760512,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNKhlMH7IpSaReyJZXf9ausIIu6lBks5shi4fgaJpZM4OGfTF
.

[davkean]

Apologies, I might be conflating things - thought I was replying to a question on a different issue, I'll let @cartermp confirm.

[vasily-kirichenko]

That's how Microsoft does OSS these days.

[davkean]

@vasily-kirichenko I was referring to the changes we made to core VS for F#.

It would be akin to making a change to editor or other IDE pieces - this code isn't open source, so we need to wait for a public build with these pieces. It's a tradeoff; F# community can spend time rewriting these pieces as open source (and less time on F#) or you can consume non-open source features/extension points and spend more time on F#.

[davkean]

As a side note, it was only the critical piece that controls the order in which source files appear in the solution tree which we had to make in the closed source tree. The extensions that add managed support _are_ all open source.

[cartermp]

@forki No public build right now. This required a fixed in closed-source parts of VS.

[kadmia]

Has this been fixed? I think I have the same issue. I just upgraded to 15.4.4 and still have the issue.

[cartermp]

This is fixed in the latest 15.5 Preview.