dotnet ws 0.1.14

• #21 Add version info for ws stop for each stopped process

Full Changelog: 0.1.13...0.1.14

dotnet ws 0.1.13

What's Changed

• #15 Bump TF to net6.0 (0.1.8)
• #13 Report if version to be stopped is not running (0.1.10)
• #16 Starting a new instance fails due to incorrect search path (0.1.10)
• #14 Revise ws build warning/error messages (0.1.11)
• #17 Command to compile F# files to JS/TS (0.1.11)
• #19 Show tool version on help (0.1.11)
• #20 Add --force to the compile command group

Full Changelog: 0.1.5...0.1.13

dotnet ws 0.1.5

The first beta release of the dotnet ws tool, shipping the following commands:

• build [--project xxx]: Build the WebSharper project in the current folder (or in the nearest parent folder). You can optionally specify a project file using --project.

• start <rid> [<version>]: Start the Booster service (wsfscservice) with the given RID and version. If no value is given for version, the latest (as found in the local NuGet cache) will be used.

• stop <version> [--force]: Send a stop signal to the Booster service with the given version. If no version is given all running instances are signaled. Use --force to kill process(es) instead of sending a stop signal.

• list: List running Booster versions and their source paths.

Changes included:

• #1 WebSharper 5 dotnet tool
• #4 Missing tools manifest
• #6 Introduce dotnet ws build to streamline compilation