Deployment of C# script applications is a simple XCOPY style distribution. Just copy your script(s) to the system that have .NET run-time and CS-Script installed and script is ready to run.
It is important to remember that .NET run-time is the only "must-be-installed" software component for success running CS-Script scripts.
If you want to run your script on the system that does not have CS-Script engine installed, you do not have to complete full installation of CS-Script. It is enough just to copy the script engine executable (cscs.exe/csws.exe) along with the script(s).
if you want to distribute your script application in a binary form and without the script engine you can generate self-sufficient executable from the script(s). Just run your script with /e switch and required .exe file (e.g. myScript.exe) will be generated for you.
When preparing the script application for deployment it is important to identify all its dependencies (if any). The Script Library contains script isolate.cs which can automatically collect all required distributable files. If you have script myScript.cs and want to prepare the distributable package for it, run the following command from command prompt:
This will create new folder myScript and all dependent files including .cs(s) and dll(s) will be copied there along with the main script file (myScript.cs). The deployment of the myScript.cs now is the matter of the copying the content of entire myScript folder on the target system.
The isolate.cs script has another interesting flavor. The following command will prepare the same package as described above and on top of it will create Visual Studio 2003 project for compiling your script into executable.
And similarly for Visual Studio 2005:
This mode of isolate.cs is particularly useful when you need to share your code with someone else in a form of Visual Studio project.