Omnisharp doesn't autocomplete with .razor files for blazorwasm app about omnisharp-vim HOT 8 CLOSED

Hi, unfortunately razor/blazor are not supported, and won't be unless someone decides to write quite a bit of code, see #546

The omnisharp-roslyn language server doesn't support them by itself. It can do using a secondary language server as a plugin but it's pretty complicated.

from omnisharp-vim.

Hi, unfortunately razor/blazor are not supported, and won't be unless someone decides to write quite a bit of code, see #546

The omnisharp-roslyn language server doesn't support them by itself. It can do using a secondary language server as a plugin but it's pretty complicated.

I was hoping that wasn't the case. I mainly mess with Azure Functions and C# api's. are Azure Functions supported? probably not?

from omnisharp-vim.

Supported how? Azure functions are just C# projects hosted on Azure, aren't they? What support would you need?

from omnisharp-vim.

I was more asking about Intellisense, such as recognizing timer triggers, and other Azure Function Specific syntax such as creating Durable Function and passing the context along to initiate activities.

I see the issue with razor files is the way the rzls.exe is licensed.

Azure functions use a secondary Azure Function Tools, I am not sure if it behaves in the same way. I will look into if it does, if so that will answer my question for me.

from omnisharp-vim.

yeah the template doesn't even show up with the dotnet command. I am going to say it is probably no dice

from omnisharp-vim.

That doesn't have anything to do with omnisharp. There are cli instructions for running azure functions tools on the command line here: https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-cli-csharp?tabs=linux%2Cazure-cli

from omnisharp-vim.

I know how to use the cli, but after importing all the packages needed after building a function using the cli, omnisharp is still throwing errors.

from omnisharp-vim.

The project hasn't loaded properly. Have a look at :OmniSharpOpenLog for details

from omnisharp-vim.