Dynamic Languages are a class of high-level programming languages that do not rely on static typing. Many decisions that are made at compile time by a statically typed language are instead made at run time by a dynamic language. For example, many dynamic languages use dynamic typing, where an object’s type is determined at run time instead of at compile time. These languages make a trade-off between compile-time type-checking in favor of increased flexibility at run time.
There are many good static languages, such as C#, and many good dynamic languages, such as IronPython. The choice of what type of language to use comes down to personal preference and to the nature of the project you’re working on.
Giving ASP.NET users the choice of languages was part of the design since our first version of ASP.NET, and this Dynamic Language Support is just another step in that direction. Unlike other Web platforms that support only one language, the ASP.NET team wants to enable users to choose the language that fits them best.
ASP.NET Dynamic Language support is currently in early Futures prototyping and can be found on the ASP.NET CodePlex website. CodePlex futures releases are early versions of code that the ASP.NET product team is actively working on, which may or may not become part of the product long-term.
In the current CodePlex release, we’ve updated the DLR support to the latest versions of the DLR and IronPython. Currently, this release does not include Language Services Support and project templates, though we plan to update this project with the new language services support when it becomes available.
Unless otherwise stated, the source code and binary files in this project should be considered early alpha builds and as such are intended for experimentation only.
Some additional resources are:
David Ebbo’s whitepaper,
Jim Hugunin’s weblog, and the
IronPython weblog.
Get the ASP.NET Dynamic Language Support CodePlex release
|
Previews Quickstarts
|
Discuss in Forums