FSharp.WebTools

Source code checked in

tomasp — Sat, 01 Mar 2008 23:37:04 GMT

Better error reporting.

Source code checked in

tomasp — Sat, 01 Mar 2008 22:52:46 GMT

Added 'build_all.bat', which compiles F# web tools.

Source code checked in

tomasp — Sat, 01 Mar 2008 22:07:55 GMT

Source code checked in

tomasp — Sat, 01 Mar 2008 22:07:41 GMT

Added testing utility, some minor changes.

NEW POST: Factoring out reusable JS compiler

andrewdavey — Sun, 16 Dec 2007 09:33:50 GMT

Another approach to consider is to follow Script# by having a "Scriptlet" ASP.NET control that is dropped on a web form.
This control then references F# types that are to be expressed as JavaScript.

NEW POST: Factoring out reusable JS compiler

andrewdavey — Sat, 15 Dec 2007 20:16:29 GMT

The current code-base is very much tied to the web forms life cycle it seems. Whilst this has its uses, I would like to use the F# to JS and server/client workflow model in different ways. For example, I am wanting to make a Model from the MVP pattern that runs on both client and server. The overall idea is to sepearate all business logic from the UI. It is conceivable to make a Model object that can run Silverlight <--> Full .NET as well as JS <--> Full .NET.

I think the winning feature of F# web tools is the workflow syntax. I've been looking at various client-server technologies. So far nothing has made the programming model seemless enough. Even Volta seems to suffer from the clunkiness of manual async callback coding.

Hmm, now there's an idea... Why not target Volta with the async workflow pattern?

Source code checked in

tomasp — Sat, 08 Dec 2007 02:48:15 GMT

Added build notes (readme.txt) and build file for tools & related.

Source code checked in

tomasp — Sat, 08 Dec 2007 02:36:35 GMT

Version compatible with F# 1.9.3.7 using final version of LINQ (some samples require .NET 3.5)

Project License Changed

Fri, 30 Nov 2007 19:24:21 GMT

Microsoft Public License (Ms-PL) This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software. 1. Definitions The terms "reproduce," "reproduction," "derivative works," and "distribution" have the same meaning here as under U.S. copyright law. A "contribution" is the original software, or any additions or changes to the software. A "contributor" is any person that distributes its contribution under this license. "Licensed patents" are a contributor's patent claims that read directly on its contribution. 2. Grant of Rights (A) Copyright Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free copyright license to reproduce its contribution, prepare derivative works of its contribution, and distribute its contribution or any derivative works that you create. (B) Patent Grant- Subject to the terms of this license, including the license conditions and limitations in section 3, each contributor grants you a non-exclusive, worldwide, royalty-free license under its licensed patents to make, have made, use, sell, offer for sale, import, and/or otherwise dispose of its contribution in the software or derivative works of the contribution in the software. 3. Conditions and Limitations (A) No Trademark License- This license does not grant you rights to use any contributors' name, logo, or trademarks. (B) If you bring a patent claim against any contributor over patents that you claim are infringed by the software, your patent license from such contributor to the software ends automatically. (C) If you distribute any portion of the software, you must retain all copyright, patent, trademark, and attribution notices that are present in the software. (D) If you distribute any portion of the software in source code form, you may do so only under this license by including a complete copy of this license with your distribution. If you distribute any portion of the software in compiled or object code form, you may only do so under a license that complies with this license. (E) The software is licensed "as-is." You bear the risk of using it. The contributors give no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this license cannot change. To the extent permitted under your local laws, the contributors exclude the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

Source code checked in

tomasp — Tue, 13 Nov 2007 14:35:08 GMT

Source code checked in

tomasp — Tue, 13 Nov 2007 14:33:09 GMT

Source code checked in

tomasp — Tue, 13 Nov 2007 14:29:43 GMT

Source code checked in

tomasp — Tue, 13 Nov 2007 14:26:33 GMT

Source code checked in

tomasp — Tue, 13 Nov 2007 14:23:12 GMT

Source code checked in

tomasp — Tue, 13 Nov 2007 13:59:39 GMT

COMMENTED ISSUE: .\build.bat not found when building FSharp.WebTools.Core

tomasp — Sun, 28 Oct 2007 23:20:15 GMT

When I open "FSharp.WebTools.sln" and right click on the "WebTools.Core" and select "Build" I get:

------ Build started: Project: WebTools.Core, Configuration: Debug Win32 ------
Compiling Project WebTools.Core ...
The compiler (.\build.bat) can not be found.
WebTools.Core build failed.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Any ideas?

Thanks
Don
Comments: ** Comment from web user: tomasp **

The project is able to find the "build.bat" file only when the solution is opened from the directory with the "sln" file, so the workaround is to open the solution by clicking on the SLN file.
Alternatively you can put a full path (on your machine) to the F# project settings of the Core & Controls projects.

Unfortunately, I don't know about any other workaround.

CREATED ISSUE: Need to create "bin"directories after downloading the source

dsyme — Sat, 27 Oct 2007 21:36:02 GMT

Running "build.bat" in the source\WebTools.Core directory on a clean download of the source gives the following error. The workaround is just to create the directory manually

C:\fsharp\src\tests\fsharp\samples\fswebtools-1\source\WebTools.Core>..\..\tools\reswriter.exe bin\webres.resx web_jslib.js web_jsatlas.js

Unhandled Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\fsharp\src\tests\fsharp\samples\fswebtools-1\source\WebTools.Core\bin\webres.resx'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, I
nt32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions o
ptions, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access,
FileShare share)
at System.Xml.XmlTextWriter..ctor(String filename, Encoding encoding)
at System.Resources.ResXResourceWriter.InitializeWriter()
at System.Resources.ResXResourceWriter.AddDataRow(String elementName, String
name, String value, String type, String mimeType, String comment)
at System.Resources.ResXResourceWriter.AddDataRow(String elementName, String
name, String value)
at System.Resources.ResXResourceWriter.AddResource(String name, String value)

at Reswriter.main@15.Invoke(String s)
at Microsoft.FSharp.Collections.Seq.iter@868.Invoke(IEnumerator`1 e@90_1)
at Microsoft.FSharp.Core.Operators.using[T,U](T ie, FastFunc`2 f)
at Microsoft.FSharp.Collections.Seq.iter[T,U](FastFunc`2 f, U ie)
at Reswriter.main()
at <StartupCode>.Reswriter._main()

CREATED ISSUE: .\build.bat not found when building FSharp.WebTools.Core

dsyme — Sat, 27 Oct 2007 21:27:17 GMT

Source code checked in

tomasp — Sat, 22 Sep 2007 23:50:43 GMT

Renamed namespaces to FSharp.WebTools.

UPDATED WIKI: Home

tomasp — Sat, 22 Sep 2007 23:48:25 GMT

Project Description
The F# Web Tools augment the F# distribution with tools to author homogeneous client/server/database web applications in one type-checked project. The modal distinctions between client and server are checked through the use of F# workflows, and LINQ can be used for database access. In the first version, parts of the application are dynamically served as JavaScript. Planned extensions include serving client-side portions as Silverlight code.

More information about the project

F# Web Tools: "Ajax" applications made simple - Blog | TomasP.Net
Rich client/server web applications in F# - Paper submitted to the ML Workshop
Ajax-style Client/Server Programming with F# - Slides from the presentation at MSR Cambridge