The short answer is: use Web sitelets. Web sitelets is how WebSharper should be used (at least since version 2.0). FPish, for example, is using Web sitelets.

HTML sitelets - if you want a static applications (that is, only HTML and JS).

ASP.NET (with or without MVC) - I wouldn't use it unless I wanted to interop with an existing ASP.NET application.

By on 1/29/2012 11:34 PM ()

I would certainly go with sitelets - either standalone or combined with an existing ASP.NET application (which is what I call "hybrid" applications.)

By on 2/5/2012 1:09 PM ()

I guess this means that while you create controls out of Formlets, and can therefore use them from ASP.NET pages if required, this would move away from expressing everything as F# code and is therefore not recommended.

Do you have any advice on the impact of using Sitelets and Formlets in a page for web useability - such as screen readers, or on SEO?

By on 2/5/2012 11:32 AM ()

Sitelets are a server-side abstraction, the content rendered is as general as you want it to be. Formlets are client-side, they initialize and render once the containing document has loaded.

By on 2/5/2012 1:14 PM ()

Thanks for clarification. I suspected that sitelets was a way to go but was not sure about when to use ASP.NET MVC templates.

By on 1/30/2012 4:24 AM ()
IntelliFactory Offices Copyright (c) 2011-2012 IntelliFactory. All rights reserved.
Home | Products | Consulting | Trainings | Blogs | Jobs | Contact Us | Terms of Use | Privacy Policy | Cookie Policy
Built with WebSharper