Actually, for the providers from FSharp.Data.TypeProviders, it's only necessary when you need to pull a schema change. You can pass `LocalSchemaFile = "foo.ssdl", ForceUpdate = false` to the provider, and it will only…
No you're right, partial classes are not supported.
Some are still pretty bullshit though. > Why drop lambda? Most Python users are unfamiliar with Lisp or Scheme, so the name is confusing To which I'd reply: Why drop class? Most Python users are unfamiliar with C++ or…
WebSharper is completely agnostic in this regard, so the question boils down to what is available for F#. The idiomatic way to deal with databases is using one of the available type providers. Basically, a TP generates…
ExtJS is GPL with paid commercial license, so essentially the same model as WebSharper. They even explicitly forbid to start developing a prototype in the open and then buy a license for it, which WS doesn't.
"Does it work with entity framework?" -> It works with whatever .NET db tool you want to use, it's entirely agnostic in this regard. "OWIN?" -> It can, with WebSharper.WebAPI [1]. "What's the story with the F# to…
Methinks it lacks "Pascal -> Need contracts -> Eiffel"
Actually, for the providers from FSharp.Data.TypeProviders, it's only necessary when you need to pull a schema change. You can pass `LocalSchemaFile = "foo.ssdl", ForceUpdate = false` to the provider, and it will only…
No you're right, partial classes are not supported.
Some are still pretty bullshit though. > Why drop lambda? Most Python users are unfamiliar with Lisp or Scheme, so the name is confusing To which I'd reply: Why drop class? Most Python users are unfamiliar with C++ or…
WebSharper is completely agnostic in this regard, so the question boils down to what is available for F#. The idiomatic way to deal with databases is using one of the available type providers. Basically, a TP generates…
ExtJS is GPL with paid commercial license, so essentially the same model as WebSharper. They even explicitly forbid to start developing a prototype in the open and then buy a license for it, which WS doesn't.
"Does it work with entity framework?" -> It works with whatever .NET db tool you want to use, it's entirely agnostic in this regard. "OWIN?" -> It can, with WebSharper.WebAPI [1]. "What's the story with the F# to…
Methinks it lacks "Pascal -> Need contracts -> Eiffel"