wcf VS omnisharp-vim

https://github.com/dotnet/wcf/issues/4887

Technically speaking WCF is quite a bit more than SOAP, I think this might be a good overview of what people used it for (or maybe use it even now).

This article is wrong. It's hard to write and requires some out of the box thinking, but it's doable. You can see my implementation here. You can't easily implement cancellability though as you can't reset the state after an await as any changes you make will happen in a copy of the Execution Context. It could be done with a custom awaiter which chains a delegate to run before the await continuation so you can reset state on the callers ExecutionContext, but I didn't need that so didn't put the effort in.

MTOM on the client is now in code review in this Pull Request. After that's merged, I'll try to find time to port it to CoreWCF in the next month.

Next in my todo list is to add support for WCF, using CoreWCF. Long term, my goal is to also support GraphQL, SignalR, ODAta and WebSockets

There is another tool xscgen, that does not collapse container types and gets all the "inner types" correct but does not generate the Input/Output types or the client interface and client. dotnet-svcutil has another bug that prevents it from reusing external types.

There is a bug in dotnet-svcutil produces incorrect types and/or annotations when collapsing SOME pure container types into jagged arrays. dotnet-svcutil does not have the option to skip collapsing. During the contract implementation phase, which happens at runtime before the first request (ugh!), the code created viaRefEmit clashes with what the annotations specify and that exception is thrown.

I thought that wcf client exists for core? https://github.com/dotnet/wcf

You can probably use omnisharp-vim (OmniSharp is the same tech that powers VS Code's C# experience).

https://github.com/OmniSharp/omnisharp-vim

https://github.com/OmniSharp/Omnisharp-vim is a thing, but I don’t know how good it is. I would probably go with VSCode or Rider (and their respective Vim plugins), as they are quite productive for .NET.

With respect to C#, have you looked at the [OmniSharp](https://github.com/OmniSharp/Omnisharp-vim) plugin?

Then use this if you don't want to use VS Code.

There's a language server for vim (and neovim): https://github.com/OmniSharp/Omnisharp-vim

Are you using omnisharp-vim? It works well in my neovim setup and configuring it was pretty straightforward!

I'm not sure if you are using the omnisharp command as an example or something you'd like to be able to do, but if it's the latter check out omnisharp-vim! I use it as my LSP for C# development and it integrates most all of omnisharp's functionality with neovim very well.

So OmnySharp has a help document „integrated“. Just type :h omnisharp-vim into vim and you should see it. Alternatively you can go to https://github.com/OmniSharp/omnisharp-vim/blob/master/doc/omnisharp-vim.txt and look at it there. In general: if a plug-in provides documentation, it’s probably stored under /doc/.txt As the c# langauage server is not a vim plug-in, it does not follow this standard. So I unfortunately can’t help with that.