Oct 01 2008

Script#: The .NET Response to the Google Web Toolkit

Published by gojko at 7:31 pm under presentations

For those of you who could not make it to Skills Matter last week, here is the video of my presentation about Script# (ScriptSharp). Script# is a free .NET tool that converts C# into JavaScript, allowing us to use a lot of existing C# tool support to write and manage large JavaScript code bases easier. This presentation introduces Script#, explains when and how to use it and discusses some common pitfalls with this tool.

Here are some related links:


Get notified when I post something new - subscribe via RSS or Twitter!

8 responses so far

8 Responses to “Script#: The .NET Response to the Google Web Toolkit”

  1. # Arjan`s World » LINKBLOG for October 2, 2008on 02 Oct 2008 at 3:29 pm

    [...] Script#: The .NET Response to the Google Web Toolkit – Gojko Adzic [...]

  2. # Robon 02 Oct 2008 at 9:47 pm

    This has got to be the craziest thing but it comes form the mind of .NET so go figure. Why in the world must one convert C# to Javascript and even have tools to do so? To modify what Laurence Olivier once told Dustin Hoffman, “Why don’t you write Javascript?”

  3. # Barton 02 Oct 2008 at 11:04 pm

    Rob:

    The reason you have to convert it is because C# doesn’t run client side. And you can write well-formed C# using Visual Studio (with intellisense, etc) whereas that would not be possible coding directly in Javascript. Did you even watch the video?

  4. # zproxyon 03 Oct 2008 at 8:37 am

    Or check out jsc that supports:
    c# -> dll -> javascript
    c# -> dll -> actionscript
    c# -> dll -> java

    http://zproxy.wordpress.com/2008/09/30/wpf-subset-powered-by-flash-and-dhtml-part-2/

    http://zproxy.wordpress.com/2008/09/25/jsc-september-2008-refresh-2/

    http://jsc.sourceforge.net/

  5. # Richon 03 Oct 2008 at 10:15 am

    Bart, are you saying that it’s not possible to write well-formed Javascript, or that you can’t get code auto-completion in Javascript? Both positions are going to be very difficult for you to defend.

    Rob, the reason tools like this exist is because the majority of developers don’t know Javascript very well and/or would prefer not to step outside their comfort zone. Developers are a surprisingly conservative bunch.

    Google implemented GWT because they have vast numbers of Java coders, and wanted to leverage that in the browser. Similarly the Microsoft-based dev community have vast numbers of C# developers.

  6. # gojkoon 03 Oct 2008 at 10:56 am

    Rich,

    it’s not just that. You do have JS intellisense for standard stuff, but (at least I have not seen an editor that does this good) for your classes. JS modularisation and dependency management is generally left to developers to do by hand as well. As I said in the talk, unless you are going to have a really complex JS code base, using Script# is an unnecessary overhead. When you have a complex code base, writing and maintaining code in an environment that can provide sort of a “compile time” check, dependency management and full type-safe intellisense for your own objects and classes can save a lot of time.

  7. # Barton 03 Oct 2008 at 2:41 pm

    Rich:

    Yes, you can write well-formed javascript. This makes it easier. And by coding in C# you get to take advantage of the full power of Visual Studio.

  8. # Arohon 07 Feb 2009 at 11:35 am

    Hi all there.
    Script# is indeed a very useful tool to write complex javascript and gives the advantage of using Visual studio and its intellisense as well as managed code. surely its not for the people like Rich who just write the Hello World applications in javascript. Developers don’t use tools just to be in comfort zone. Its the matter of productivity and achievement. Why do you use Visual Studio? You can code in notepad and compile your code in a command line compiler.

Trackback URI | Comments RSS

Leave a Reply