I've been musing over F# and ASPX MVC, and came across this excellent blog.

[link:codebetter.com]

Good instructions on how to do it, and a few thoughts on why.

By on 11/23/2008 7:42 PM ()

Hi,
funny that you're asking :-) The first article on the hubFS web page answers this question:
[link:cs.hubfs.net]

There is also a project that attempts to make it possible to write client-side scripts running in web browser in F# and simplify communication betwee server-side and client-side. More info is here: [link:tomasp.net]. It was a bit inactive recently, but I'm hopefuly going to get back to it and make it ready for the "commercial version of F#" soon!

T.

By on 7/24/2008 7:20 AM ()

Tomas, how about an example for F# with ASP.NET MVC? I don't like regular ASP.NET and to be honest i don't think F# is a good choice for it. The examples that i've seen are actually more convoluted than if they were written in C#. Perhaps ASP.NET MVC is a better match for a functional language like F#. But i think that a really good web framework has to be written specifically for F#.

By on 7/24/2008 1:51 PM ()

This has been an interesting thread.

Would you mind telling me the difference between ASP.NET and ASP.NET MVC?

And, can any one tell me what programming languages etc, one would have to know in order to go ahead and create a web framework for F#? Obviously this language (F#) is the wave of the future. I'd like to contribute to that if I can.

Thanks.

Dab

By on 11/10/2008 5:28 PM ()

> Would you mind telling me the difference between ASP.NET and ASP.NET MVC?

ASP.NET MVC is a new framework from Microsoft for developing database driven web sites, using ASP.NET. You could call it a layer on top of ASP.NET. You probably shouldn't be looking at it until you are familiar with ASP.NET. It is Microsoft's answer to Ruby on Rails.

> Obviously this language (F#) is the wave of the future.

I don't know how you picked that up, being new to programming, but you may be right - although no single language will ever replace all the others!

I like your enthusiasm!

Good luck with it all.

By on 11/11/2008 7:24 PM ()

ASP.NET MVC is a generic framework, not just for database driven sites.

It has little to do with ASP.NET other than using it as the viewing engine and definitely not on top of ASP.NET.

You don't need to know much about ASP.NET in order to use MVC, they are concentually very different thing, so not knowing it may be better.

I doubt F# would be the wave of the future but learning to think functional(immutable in general) makes me a better coder.

By on 11/12/2008 11:05 PM ()

Gary...

"It has little to do with ASP.NET other than using it as the viewing engine and definitely not on top of ASP.NET."

This is inaccurate. ASP.NET MVC is ASP.NET. Now, saying "run as part of" may be more accurate than saying "run on top of", because ASP.NET MVC does not hide any of the features or functionality of ASP.NET. However, they are not terribly different when you get right down to it. The confusion, I think, might stem from the fact that ASP.NET tried for so long to emulate the VB6/WinForms model of development. It actively hide much of the framework behind cumbersome design-time processes. ASP.NET MVC, in so much as it embraces rather than hides the stateless nature of HTTP, may make it seem like something wholly different, but it is not. ASP.NET is NOT ASPX/ASCX/ASMX files. ASP.NET is a managed web stack composed of HttpApplication instances fronted by a request/response pipeline composed of IHttpHandler and IHttpModule instances. Anything running under that model, including ASP.NET MVC, is ASP.NET. In fact, that's why its call "ASP.NET MVC" and not "MVC.NET". Make sense?

By on 12/30/2008 7:29 PM ()
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