Notes from 03 03 2013 Discussion

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
• 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
3. Very conscise and clear error handling
4. I can include other loose scripts.
5. I can have a nuget package with scripts
6. I don't need to install anything including RosylnCTP.

Roadmap - Priority in [ ]

• [1] Validate against Packages.config - Only load packages in the config, error if packages are missing. (Glenn)
• [1] Includes - #Load don't reinvent / be consistent (Filip)
• [1] Scriptcs API - ALlows hosting Scriptcs (Justin)
• [1] Validate binaries in scripts are present in bin.
• [2] C# interactive window support (Filip)
• [2] Script packs - 3rd party plugins (Glenn) ** Nuget script pack? Some tag or file that says it's a pack ** Script nuget package binding - I can have a nuget with scripts ** Host object contains property per script packs
• [2] Export to exe
• [2] Export to VS Project
• [2] Sublime Text Plugin
• [2] Syntax tree validation ** Are my script packs present? ** Are all my nuget packages present?

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

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