Add Support for F# Code-Behind ASP.NET
Elevating F# to a more equal footing with VB and C# for ASP.NET
I am planning to decline this request, as it is currently in the context of WebForms and the recent comments have indicated no desire for F# support for web forms.
This is currently the #1 requested item on ASP.NET UserVoice - but I'm seeing a lot of 'astro-turfing' in response to my comments about considering closing this in response to the three individuals who indicated that they wouldn't use F# with web forms.
The number of anonymous users who are voting for this, with no comments to support our decision leads us to think that this number is artificially inflated and not indicative of actual developers who would use the framework in this way.
If you do feel strongly about F# with Web Forms - please add a comment describing what you are looking for. The influencers who have significant votes and commented many times throughout the .NET UserVoice space have indicated that this is not needed - I need your voices to help us make this decision.
Gauthier Segay commented
A more progressive approach (than declining the request, which apparently has still lots of votes) would be to initiate support for webforms, based on F# CodeDomProvider, and provide an opensource project for that support.
People interested in it will maintain it, and people who want to learn how to release support for "non sanctionned" languages will be able to use the project as a pattern to make this happen for other languages.
I agree this is probably not a relevant request anymore - especially now that F# has a great web story on its own with projects like Suave (http://suave.io).
Eriawan Kusumawardhono commented
I'm sure that there are lots of interests of having ASP.NET designer with code behind.
Please don't compare the number of votes with the rest of ASP.NET user voices, because most of ASP.NET developers don't use F#. It would be unfair for us, F# developers.
Also F# is not just MS Research idea, it's been productized for more than 5 years since its inclusion with Visual Studio 2010 as one of .NET first class programming language that is integrated with Visual Studio.
Asbjørn Ulsberg commented
I'm either with Thomas Petricek or Mark Seeman on this. The former if you redefine the scope of this request from WebForms code-behind to all of ASP.NET (especially MVC and Web API) or the latter if the scoe remains the same. I'll keep my vote for now and see how this develops.
Mark Seemann commented
This request is almost four years old, and I think it'd be a mistake to interpret votes given years ago as current interest. So much has happened since then that I'd be sorry to see the Visual F# team waste its limited resources on this. For that reason, I hereby retract my votes (that I placed so long ago that I don't even remember doing it).
@Rick Anderson - Thanks for taking the time to review this. I think most of the votes for this issue have been simply saying "improve F# support" in ASP.NET - no matter if the technology is (now outdated) web forms, or more recent MVC framework.
I'll happily submit a new issue, but wouldn't it make more sense to change the tags for this so that it applies to both WebForms and MVC?
Nick Lechnowskyj commented
This request is a waste of time. Now that MVC is out and mature I'm not sure why anyone's creating new projects in Webforms. It's an absolute horrible and inneficient way of working with HTTP
Ryan Riley commented
I am surprised that Xamarin Studio offers this before Visual Studio. Does this mean that the limitation is entirely a support decision and that nothing actually stops the runtime from running F# projects on the server?
I think it also important to note that all ASP. NET frameworks should be supported, including MVC and Web API.
I would also love to see this. Writing F# has been a great experience and I think ASP.NET applications can benefit greatly from the stuff F# brings to the table.
Talbott Crowell commented
Please place F# on equal footing with VB and C# for support in ASP.NET. F# is the only functional-first language in the .NET space.
John Tarbox commented
As a Windows developer since Windows 2.0, I can honestly say that F# is one of the best things to come from Microsoft. It is time to make it a full member of the .NET family and improve the tooling and tinplating support. Choosing between VB.Net and C# for code behind is really no choice at all; F# offers a truly different alternative with substantial advantages in many use cases.
Jack Fox commented
As a professional with 30 years experience in application engineering development and management, I have seen bona fide technologies and fads come and go. I am skating to where the puck is going to be. Functional languages are here to stay, and over time will gain a larger role in most areas of application development. It has not gained the attention of marketers, yet, but more and more pros know what I am talking about. F# is a superior technology that MS should be paying more attention to.
I would really love to at least have an F# web application project template. I use FubuMVC and that's all I need to get going. The F# web dev story is pretty weak compared to C# and I'd love to see that change. The web is where its at for the foreseeable future and I think 1st class support will be a key ingredient in pushing F# into the mainstream.
As an F# MVP who is interested in web programming, I would love to see this issue addressed in one way or another.
Of course, the perfect solution would be full F# support (for writing code-behind in ASP.NET Web Forms and for writing models & controllers in the ASP.NET MVC framework and also as a language supported by the Razor engine).
This should not be too much work, but I can imagine that the F# community does not need all of those. For example, the MVC model fits more naturally with functional languages, so I find supporting F# in ASP.NET MVC more important than WebForms. Moreover, I'm happy to write C# code in the Razor view code (although F# would be very nice there).
So, having at least an ASP.NET MVC project template that uses F# for writing model & controller components would be a huge step forward and I think it would enable most of the scenarios - such as integrating awesome F# data access features like F# 3.0 type providers in web applications.
The following feedback item along with votes was transferred from the Visual Studio User Voice site. If you would like to view the original comment history, click here http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2315429-add-support-for-f-code-behind-asp-net