Projects require preliminary dotnet restore for editor to provide features
#66
Labels
Comments
mickaelistria
added a commit
that referenced
this issue
Aug 1, 2017
Signed-off-by: Mickael Istria <[email protected]>
mickaelistria
added a commit
that referenced
this issue
Aug 1, 2017
Signed-off-by: Mickael Istria <[email protected]>
mickaelistria
added a commit
that referenced
this issue
Aug 10, 2017
Update of omnisharp-node-client removed requirements for `dotnet restore` Signed-off-by: Mickael Istria <[email protected]>
LucasBullen
pushed a commit
to LucasBullen/aCute
that referenced
this issue
Nov 21, 2017
Re-add previously removed workaround for OmniSharp/omnisharp-node-client#265
LucasBullen
pushed a commit
to LucasBullen/aCute
that referenced
this issue
Nov 21, 2017
Re-add previously removed workaround for OmniSharp/omnisharp-node-client#265 Signed-off-by: Lucas Bullen <[email protected]>
LucasBullen
pushed a commit
to LucasBullen/aCute
that referenced
this issue
Nov 21, 2017
Re-add previously removed workaround for OmniSharp/omnisharp-node-client#265 Signed-off-by: Lucas Bullen <[email protected]>
LucasBullen
pushed a commit
to LucasBullen/aCute
that referenced
this issue
Nov 21, 2017
Re-add previously removed workaround for OmniSharp/omnisharp-node-client#265 Signed-off-by: Lucas Bullen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Most projects require users to first run
dotnet restoreon a project before the editor (the underlying LS actually) provide most features. This is caused by OmniSharp/omnisharp-node-client#265Invoking
dotnet restoreshould be made automatically when starting up the LS so user isn't expected to do anything else.The text was updated successfully, but these errors were encountered: