New VS Extensibility SDK - Can F# be Used for Extensions ?

[ghost]

Hi,

Visual Studio has a new extensibility SDK:
https://learn.microsoft.com/en-us/visualstudio/extensibility/visualstudio.extensibility/?view=vs-2022

Can F# be used with this?

Thank You

[T-Gro]

Hello @CodePagesNet .

We do use the same model for creating the F# LSP visual studio extension.
Part of the new extensibility model uses C# source generators, so the startup project and the basic definition is done as a C# project. Anything else, including attribute-annotated command processors and endpoints, is done within an F# project.

One this new extension is more mature, we can publish the findings to act as learning material - both on how to do VS development using the new SDK, as well as steps needed to develop an extension providing language services via LSP.

[vzarytovskii]

It can't, it uses source generator to generate manifest. You can generate manifest yourself, but that won't be sustainable long term, and will likely lead to some inconsistencies as SDK evolves.

[ghost]

Thanks kindly, @T-Gro and @vzarytovskii,

Mr. Zarytovskii (Vlad), are you referring to old .NET Framework extensibility model? I'm referring to the new one (see link in OP). In fact, it was my perception of lack of code generation (e.g. vsct) that encouraged me that F# can be used. Are you speaking of the [(...Contribution)] attribute?

Do you concur with Mr. Grosup (Tomas) that F# can be used for 90% of code base as long as C# is used where needed?

Also, C# can use F# libraries with no problem (provided same .NET version etc.) true?

[vzarytovskii]

Yes, sorry, I was imprecise in my wording. As Tomas already mentioned, extension can be 90% written in F#, i.e. business logic. It's just the main project will have to be C#, due to the codegen (including Contribution attribute) for the manifest generating.

C# and F# can both use each other libraries, that's correct.

[ghost]

OK thank you!