This document provides information about ScriptCS, an open source project that enables rich C# scripting. Some key points: - ScriptCS allows users to write and execute C# scripts or use a REPL without compilation or projects. - It has over 500 watchers on GitHub and contributions from 29 developers. - ScriptCS uses Roslyn and NuGet under the hood and supports features like script packs, debugging in Visual Studio, and a Sublime Text plugin. - Script packs allow extending ScriptCS with additional functionality through references, namespaces, and exposed methods. Popular packs include NUnit for testing and RavenDB for document databases.

2. scriptcs.net
@scriptcsnet
www.scriptcs.net

3. scriptcs.net
@filip_woj
github.com/filipw
www.strathweb.com
www.arcmedia.ch

4. scriptcs.net
Who is scriptcs?
 Community (!)
 Coordinators
 Glenn Block (@glennblock)
 Justin Rusbatch (@jrusbatch)
 Filip Wojcieszyn (@filip_woj)
 Core Commiters
 Damian Schenkelman (@dschenkelman)
 Kristian Hellang (@khellang)

5. scriptcs.net
Metrics
 525 watchers
 110 forks
 142 pull requests
 29 unique contributors
 14 community contributed script packs (extensions)
 Currently at v0.5

6. scriptcs.net
Khalid AbuhakmehIan Battersby Nick Berardi Glenn Block Scott Blomquist Danielle Boldt Tim Erickson
Jonas Follesø Victor Grigoriu Andreas Håkansson Kristian Hellang lbargaoanu Denis Mentey John
Nelson Alexander Nyquist David Pendray Aaron Powell Adam Ralph Justin Rusbatch Damian
Schenkleman Paul Shmakov Lodewijk Sioen Brandon Stirnaman Paul Stovell Patrik Svensson Kevin
Trethewey Michael Wade Filip Wojcieszyn Matt Wrock
Contributors

7. scriptcs.net
What is scriptcs?
 OSS project enabling rich C# scripting experience
 Script and execute -or- use REPL
 Robust extensibility model
 Low ceremony, lightweight
 Use your favorite text editor
 No compilation/projects/solutions
 Built on top of Nuget & Roslyn (no hard dependencies)

8. scriptcs.net

9. scriptcs.net
Scriptcs overview
scriptcs
Script Engine
Package
Management
Script Packs

10. scriptcs.net
Key scriptcs features
 Relaxed C# syntax & code semantics
 As defined in “Interactive C#/VB REPL and Script - Code
Semantics Spec“ white paper
 REPL
 Node.js-like extensibility model (script packs)
 Debug & step through in Visual Studio
 Sublime text plugin
 Scriptcs.Core available as a hostable service
 Nuget integration

11. scriptcs.net
Scriptcs model
Roslyn / Mono.Csharp*
Nuget
OSS libraries MEF

12. scriptcs.net
OSS libraries used by scriptcs
 Autofac (dependency injection)
 Common Logging, log4net (logging)
 LiteGuard (argument checks)
 Nuget Core (package installation as a service)
 PowerArgs (command line parsing)
 ServiceStack.Text (serialization)
 Moq, xunit, Should (testing)

13. scriptcs.net
Getting started with script
Get
packages*
• Scriptcs -install
Write
code
• Any editor
Execute • CLI or hosted

14. scriptcs.net
Demo: Getting started with script

15. scriptcs.net
Demo: #load & #r

16. scriptcs.net
Getting started with REPL
Get
packages*
• Scriptcs -install
Run
scriptcs
Write
code
Evaluate

17. scriptcs.net
Demo: Getting started - REPL

18. scriptcs.net

19. scriptcs.net
Script code semantics
 No top level class
 No arbitrary namespaces
 No Main method
 Global functions allowed
 Script packs accessible through Require<T>
 #load directive to load script from script
 #r directive to reference an assembly from script

20. scriptcs.net

21. scriptcs.net
Typical C# experience
 Start Visual Studio (...wait...)
 Choose VS project template
 Create new solution
 Add references, install Nuget packages, import
namespaces
 Compile
 Run (repeat: compile+run)
 Difficult to distribute source code (bloated)

22. scriptcs.net

23. scriptcs.net
Typical scriptcs experience
 Install Nuget packages with “scriptcs –install”
 Write code in any text editor
 Run (repeat: edit & run)
 Easy to distribute code (just CSX + packages.config)

24. scriptcs.net
Self hosted server – traditional C#

25. scriptcs.net
Self hosted server – scriptcs / node.js

26. scriptcs.net
Demo: Nancy

27. scriptcs.net
Role of script packs
Import references
Import namespaces
Expose functionality

28. scriptcs.net
Script pack example: NUnit
 References
 nunit.core.dll, nunit.core.interfaces.dll, nunit.framework.dll
 Namespaces
 Nunit.Framework, System.Reflection
 Functionality
 public TestResult RunAllUnitTests(Assembly testAssembly =
null)
 public TestResult RunAllUnitTests(Action<string> callback,
Assembly testAssembly = null)

29. scriptcs.net
scriptcs Nuget integration
 Developed to work around nuget.exe limitations
 scriptcs –install
 Gets all packages from packages.config with dependencies
 scriptcs –install <package name>
 Gets specific package with dependencies
 scriptcs –save
 Creates packages.config based on packages folder
 scriptcs –clean
 Gets rid of packages folder and unnecessary binaries

30. scriptcs.net
Demo: RavenDB

31. scriptcs.net
Demo: P/Invoke

32. scriptcs.net
Demo: WPF

33. scriptcs.net
Get scriptcs
 CLI distributed via Chocolatey
 cinst scriptcs
 Libs available on Nuget
 Nightly builds on MyGet
 Build from source
 github.com/scriptcs

34. scriptcs.net
What’s next?
 Pluggable CLI commands
 Pluggable REPL commands
 Export to Visual Studio solution
 Mono support
 Script packs as scripts
 ScriptCatalog – extend applications (MEF) with scriptcs
 Improved ScriptCs.Core API

35. scriptcs.net