3 ms·
The support for F# in VS leaves a lot to desire, indeed. However, in my experience, I've found that the developer productivity gains from F# outweigh the inconv
by dgudkov 7y ago
The support for F# in VS leaves a lot to desire, indeed. However, in my experience, I've found that the developer productivity gains from F# outweigh the inconvenience.
- pjmlp 7y agoOnly if what you are doing is directly supported by F#. If you attempt to do GUI development, then you are forced to look for community projects like Fabulous, use the XAML type provider with a dummy C#,VB.NET,C++/CLI project for the XAML generation, or actually use one of those languages for the UI, with F# used only for the logic. So even though I am a big fan of ML language family, at the end of the day, the other .NET languages get the green light from most customers and team.
- WorldMaker 7y agoI don't recall having too much difficulty getting the VS WPF XAML Designer to basically function with F#. Some features just don't light up like event connecting/code-behind, but that's fine and what I wanted anyway (taking an MVVM-ish approach). There's a hope that with F#'s upcoming move to the "shared project system" that a lot of the pains will go away in hopefully the near future. (That said, Fabulous has piqued my interest and I'm debating rewriting my big F# GUI in it, at least in an exploratory branch.)