Code Runner .NET

Source code checked in, #99885

Project Collection Service Accounts — Mon, 01 Oct 2012 21:24:31 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #99884

Project Collection Service Accounts — Mon, 01 Oct 2012 21:16:08 GMT

Checked in by server upgrade

Updated Wiki: Home

jlyonsmith — Wed, 04 Aug 2010 01:01:02 GMT

Summary

Code Runner .NET provides the ability to run C# source files directly from the command line just as if they were scripts. Tools are provided to allow you to easily edit and debug the script with the full power of the Microsoft Visual Studio programming environment.

Code Runner .NET has moved!

You can now find the project on http://bitbucket.org/jlyonsmith/coderunner/wiki/Home. New releases will appear there. Releases that are currently on this site will remain, but all new releases (including VS2010 support) will come from the BitBucket.org site.

So long Microsoft, and thanks for all the fish!

Updated Wiki: Home

jlyonsmith — Wed, 04 Aug 2010 01:00:43 GMT

Summary

Code Runner .NET has moved!

You can now find the project on http://bitbucket.org/jlyonsmith/coderunner/wiki/home. New releases will appear there. Releases that are currently on this site will remain, but all new releases (including VS2010 support) will come from the BitBucket.org site.

So long Microsoft, and thanks for all the fish!

Updated Wiki: Home

jlyonsmith — Wed, 04 Aug 2010 01:00:16 GMT

Summary

Code Runner .NET has moved!

You can now find the project on http://bitbucket.org/jlyonsmith/coderunner. New releases will appear there. Releases that are currently on this site will remain, but all new releases (including VS2010 support) will come from the BitBucket.org site.

So long Microsoft, and thanks for all the fish!

Updated Wiki: Home

jlyonsmith — Wed, 04 Aug 2010 00:58:46 GMT

Summary

Code Runner .NET has moved!

You can now find the project on [http://bitbucket.org/jlyonsmith/coderunner]. New releases will appear there. Releases that are currently on this site will remain, but all new releases (including VS2010 support) will come from the BitBucket.org site.

So long Microsoft, and thanks for all the fish!

Updated Wiki: Home

jlyonsmith — Wed, 04 Aug 2010 00:58:13 GMT

Summary

News

Code Runner .NET has moved! You can now find the project on [http://bitbucket.org/jlyonsmith/coderunner]. New releases will appear there. Releases that are currently on this site will remain, but all new releases (including VS2010 support) will come from the BitBucket.org site.

So long Microsoft, and thanks for all the fish!

Updated Wiki: Background

jlyonsmith — Tue, 03 Aug 2010 23:39:00 GMT

Background

The glue of the software development industry is the //script//. A script is a typically a small program that performs some mundane but essential task. Scripts are typified by the following:

They are usually a single file program that controls the flow of execution of other scripts or programs. The file constitutes both the source code and the executable entity. Once the script source is typed in, it can be run with only a single conscious step. Typing the name of the script inside an appropriately configured console shell is usually sufficient.
They are usually written in a scripting language such as Windows Command Shell, VBScript, JScript, Perl, Python, Powershell and so on. These languages have the attribute that they can interpret and run the script source directly (see above) and that they provide a rich variety of utility functionality, such as regular expressions, environment variable control, and input/output piping for console applications. In contrast non-scripting languages such as Visual Basic, C# and C usually require multiple steps to turn source into a runnable program.

Another way to say it is that scripts are all about instant gratification. However scripting languages are usually weak in several ways:

Many scripting languages lack a powerful integrated development environment. Most script developers use simple text editors to write the script. This means they are not able to take advantage of the power of modern tools, which include such features as integrated help, code coloring, Intellisense® and so on.
Some script languages are write only. Scripts can be hard to understand, even if you wrote the script yourself. Some languages, such as Perl and Awk are notorious for this and such scripts can be very difficult for others to maintain.
Most importantly, most script languages lack a powerful debugger. Many, such as Windows batch files lack a debugger at all, and are subsequently very difficult to troubleshoot.

The .NET platform on Windows provides tremendous functionality. In particular the libraries that ship with .NET provide much of the functionality that script writers cherish, such as regular expression support. In particular:

.NET provides powerful languages such as C# and Visual Basic .NET that are easy to learn.
The .NET language compilers are fast. The C# compiler in particular is able to compile even reasonably large amounts of source into runnable code in sub-second times.
Hobbyist versions of the Visual Studio development environment are available for free, and provide a state of the art development environment and debugger.

The Code Runner .NET project is about investigating ways to bring the script writing community together with the existing .NET languages and Visual Studio tools and so make the task of script writing easier and more enjoyable.

Why is the project called Code Runner? The term "running code" probably has some roots in old home computer basic languages that typically use the "RUN" command to cause the users program to execute. Typically programs in languages such as C# are not directly runnable, but this project makes them appear to be so.

=== Functionality ===

At it's core Code Runner .NET is composed of the following components:

A code runner.** For C# programs this is a console program called csr.exe. This program is passed file containing C# source (typically with a .csr extension) , compiles it and runs the resulting image. The program also caches the resulting image, so that future invocations will be faster.
A scaffolding erector.** This program is called scaffold.exe. The purpose of this program is to erect project scaffolding around a .NET program so that the full power of the Visual Studio environment can be used to edit and debug the script. When Visual Studio exits, the scaffolding is torn down and deleted leaving just the "runnable" program file.
A library of utility routines. These enhance the .NET run-time Base Class Library (BCL) with additional features needed when writing scripts like programs. This library is called CodeRunner.dll.
Sample scripts.** The tool comes with a collection of sample scripts for you to use, modify and extend.

=== Community Benefits ===

Code Runner .NET is intended to provide the following developer community benefits:

Enhance the adoption of Visual Studio as the best way to develop for .NET and Windows.
Enhance the adoption of .NET languages such as Visual Basic .NET and C#.
Provide a faster easier way to write and distribute small utility programs for .NET and Windows.
Enhance understanding of the power of .NET's dynamic code compilation capabilities.

Source code checked in, #74794

_TFSSERVICE — Tue, 03 Aug 2010 19:44:57 GMT

Checked in by server upgrade

Created Issue: Add support for .NET 4.0 to CSR [28104]

jvstein — Thu, 15 Jul 2010 17:23:14 GMT

I did this on my local copy of Code Runner .NET. It involved upgrading the entire solution to Visual Studio 2010 and switching the target framework over to 4.0. After that, CSR was able to compile scripts dependent on 4.0 features.

There are probably other things that need to be updated (Setup?), but this worked for my purposes.

Commented Issue: Use relative paths in rsp file when possible [28103]

jvstein — Thu, 15 Jul 2010 16:59:15 GMT

It's better to use relative paths in the rsp file. That way you can put a CSR script (with it's RSP file) in SVN, it can reference another project in the same SVN repo and you don't have to worry that everyone check out the repository to the same location or drive.
Comments: ** Comment from web user: jvstein **

Added patch 6343 with these changes.

Patch Uploaded: #6343

jvstein — Thu, 15 Jul 2010 16:58:38 GMT

jvstein has uploaded a patch.

Description:
Makes the rsp file contain relative paths when possible.

Created Issue: Use relative paths in rsp file when possible [28103]

jvstein — Thu, 15 Jul 2010 16:57:00 GMT

Patch Uploaded: #6342

jvstein — Thu, 15 Jul 2010 16:49:04 GMT

jvstein has uploaded a patch.

Description:
Adds support for using VS 2010 via scaffold.

Moving the patch over here, from the related issue.

Patch Uploaded: #6341

jvstein — Thu, 15 Jul 2010 16:47:14 GMT

jvstein has uploaded a patch.

Description:
Fixes the default debugging directory on x64 machines.

Commented Issue: Support Visual Studio 2010 [26911]

zespri — Thu, 15 Jul 2010 11:32:54 GMT

The attached patch adds support for Visual Studio 2010 solution files.

--Jeff
Comments: ** Comment from web user: zespri **

Thanks a lot!

Created Issue: Support Visual Studio 2010 [26911]

jvstein — Wed, 28 Apr 2010 18:19:08 GMT

The attached patch adds support for Visual Studio 2010 solution files.

--Jeff

Reviewed: Code Runner .NET 3.1 (Sep 10, 2009)

pipelinecache — Thu, 10 Sep 2009 13:51:39 GMT

Rated 4 Stars (out of 5) - Neat stuff!

Updated Release: Code Runner .NET 3.1 (Aug 12, 2009)

jlyonsmith — Wed, 12 Aug 2009 20:35:52 GMT

New Features

Csr MSBuild task now has a ToolPath attribute and has predictable search order
RemoteEnvironment class now supports getting all the environment variables in another process

Bug Fixes

Scaffold projects are x86 so they work on x64 versions of Windows.
Return non-zero error code from csr.exe when .NET 3.5 not installed or when script throws exception.

Released: Code Runner .NET 3.1 (Aug 12, 2009)

Wed, 12 Aug 2009 20:35:52 GMT

New Features

Csr MSBuild task now has a ToolPath attribute and has predictable search order
RemoteEnvironment class now supports getting all the environment variables in another process

Bug Fixes

Scaffold projects are x86 so they work on x64 versions of Windows.
Return non-zero error code from csr.exe when .NET 3.5 not installed or when script throws exception.