F# C# MVC 4


F# and C# Web Application template by Daniel Mohl that produces a ASP.NET MVC 4 solution (ASPX or Razor View Engine). Note: You need to have ASP.NET MVC4 installed (see http://www.asp.net/mvc/mvc4).

(1) Review
Visual Studio
2015, 2013, 2012, 2010
Download (149,914)
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Reviews (1)
Q and A (4)
Sign in to write a review
Sort by:

by JamesFJr80 | March 06 2013

Finally, the ability to use F#'s powerful functional paradigm within my web apps. Thank you!

Sign in to start a discussion

  • Not able to download or update
    2 Posts | Last post January 03, 2014
    • Does anyone have an issue with getting the update.  I can get all other VS2013 updates, but this one always stops at 8.42MB.  Any significance with this number?
      Thanks in advance for any help.
    • I haven't experienced this issue, but I'll look into it. In the meantime, you should be able to download the file from this page, double-click to install, and restart VS to get the update.
  • Incorrect MVC reference
    9 Posts | Last post June 10, 2013
    • There seems to be an issue in FsCsMvc41WebApp.fsproj, as it has a GAC reference to MVC:
      <Reference Include="System.Web.Mvc, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL" />
      Instead, it needs to have a NuGet reference, as in FsCsMvc41Web.csproj:
          <Reference Include="System.Web.Mvc, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
      The causes the build to break when MVC4 is not in the GAC. See this thread for reference: https://github.com/projectkudu/kudu/issues/137
    • It looks like this may only be an issue with the "Empty Project" template. I'll push a fix this weekend.
    • It should be fixed now with version 1.15. Let me know if you run into anything else. Thanks!
    • Yes, looks good now, thanks!
    • Hmmm, along the same line but not quite the same: the fsproj has a reference to ..\..\packages\System.Net.Http.2.0.20710.0, but it doesn't look like that NuGet package actually gets installed. Same for the other System.Net.Http.* packages.
      Also, interestingly, the F# project doesn't have a packages.config at all, but seems to rely on the packages that came with the C# proj.
    • I believe that I've fixed the issue, but it will take some time to fully test. I hope to release it within the next week. Thanks for the great feedback!
    • For some reason, when I programmatically install the packages in the F# projects the references are not added the same way that they are in the C# web project. Any thoughts as to why that would be?
      As a work around, I've added the references and packages.config file via a typical project template approach. This is certainly a hack, but it allows the references to be correct in the .fsproj files and appears to also allow the NuGet update/uninstall/etc functionality to work as expected.
    • I used whatever version was in Nuget yesterday for my blog post, and all I had to do was target the F# project at .NET 4.5. Is 4.5 the intended target? http://sireel-world.azurewebsites.net/sir-eel-visions/WATK-FS-Pt2
    • I believe that the default framework target issue is now fixed in version 1.17. Let me know if you run into anything else.
  • getting it to work
    2 Posts | Last post August 25, 2012
    • I can't seem to get this template to work. I got VS 2010 Pro and have installed ASP.NET MVC 4 as instructed yet any attempt to start a new project fails.
    • Sigh. I just found out why. The web install of ASP.NET had failed silently to update my VS 2010 install properly. The downloadable installer did work though so now I'm golden :)
  • what is the template called
    3 Posts | Last post December 07, 2011
    • I have installed this template with no errors in VS2010. (With MVC 4 installed)
      Yet I don't find it anywhere in my templates?
    • It should show up under Visual F# | ASPNET with the name "F# and C# Web Application (ASP.NET MVC 4)". Check the installed extensions (Tools | Extension Manager...) and verify that this extension is enabled. 
    • =Cool