Skip to content
khellang edited this page Apr 3, 2013 · 1 revision

Values

  • Simplicity - don't try to reproduce VS, no need to RTFM
  • Agility
  • Having a platform for fast development / easily grow up

Use cases

  • Prototype quickly
  • Build simple apps
  • Write automation scripts i.e. like Ruby/Node
  • Initialization like startup/bootstrapping type of things.
  • Extensions / Extending an app with Script

Acceptance criteria

  1. I don't need to read a manual.
  2. I don't need to install anything other than scriptcs including the Roslyn CTP
  3. I can see very clearly when things go wrong
  4. I can include other loose scripts.
  5. I can have a nuget package with scripts

Roadmap - Priority in [ ]

  • [1] Validate against Packages.config - Only load packages in the config, error if packages are missing. (Filip) DONE
  • [1] Includes - #Load don't reinvent / be consistent (Filip) DONE
  • [1] Scriptcs API - Allows hosting Scriptcs (Justin) DONE
  • [1] Validate binaries in scripts are present in bin.
  • [1] Team city build. DONE
  • [2] C# interactive window support (Filip)
  • [2] Script packs - 3rd party plugins (Glenn) DONE
  • [2] Export to exe
  • [2] Export to VS Project
  • [2] Sublime Text Plugin DONE

Won't do - Though community can do it with script packs.

  • ASP.NET on IIS?
  • MVC / Web Forms?
  • Create DLLS