Nikhil Kothari's Weblog : Some Early Script# Projects

Some Early Script# Projects

Pointers to a few Script# projects and related works from a tutorial to a VS add-in to an actual commercial offering...

Some interesting projects built upon Script#:

First Simon wrote an IPv4 masked edit control, and published a tutorial that provides a nice step-by-step guide of using Script# to write script libraries using ASP.NET AJAX and then packaging them into server controls.
Simon mentioned he is going to publish a few new things as well, and sure enough, today he published a VS add-in that generates C# proxies for Web services that can then be used and compiled along with the rest of your C# code to be turned into script. This is a feature that makes a lot of sense, but I couldn't get to in the 0.3 time-frame. Its great to see some community love.
Finally, Stephen mentioned to me in mail a while ago, but now mentioned it publicly in his comment - looks like the new SoftwareFX Grid component for ASP.NET benefited from Script# during development.

I know of a few other projects using Script# from past mail exchanges ... so if there is something you want to share, please go ahead... either through my comment form or the contact form.

[ Tags: script# | ajax | javascript | projects | announcements ]

Posted on Thursday, 5/31/2007 @ 7:58 AM | #Script#

Comments

7 comments have been posted.

Dan Goldstein

Posted on 5/31/2007 @ 9:45 AM

In Simon's tutorial, he had to create separate projects for the Script# files and the Control Library. Are there plans to allow Script# files to be in the same project as the web site or a control library?

Nikhil Kothari

Posted on 5/31/2007 @ 12:25 PM

Dan... the short answer is no. Longer answer:

The reality is that the code you compile against script# is referencing a different set of assemblies than the code you write for implementing the server control itself. I know what you're asking for is logical projects where the server-side code and client-side code can be part of the same project... but mixing the files doesn't work. Both the c# compiler and script# compiler would try to compile *.cs within the project and that wouldn't work. Choosing a different file extension also doesn't work, since you actually want to get the c# editing experience.

In reality logical projects do exist - a single solution contains multiple projects... from the perspective of a solution, each physical project is akin to a logical project.

Stuart Leeks

Posted on 5/31/2007 @ 11:46 PM

Couldn't you pick a custom extension and then map that to the C# text editor? (Tools/Options/Text Editor/File Extensions). I've used this to map jsx files to the Script Editor to make life easier for working with your javascript minimiser.

Eddy Recio

Posted on 6/6/2007 @ 9:47 PM

I posted a few S# controls a while back.
windark.net/blog/PermaLink,guid,3b507c5e-6739-4c56-9b8b-f3bcb7fde9fb.aspx

Simon FERQUEL

Posted on 6/8/2007 @ 4:03 AM

I have just published a video on my blog, presenting a sample project with Script#, ASP.Net Ajax, and Web Services (it uses my add-in to allow script# scripts to call WS).

Simon FERQUEL

Posted on 6/8/2007 @ 4:09 AM

blogs.labo-dotnet.com/simon/archive/2007/06/08/17379.aspx

Alexey Kucherenko

Posted on 7/19/2007 @ 4:52 AM

Very interesting example.
Thanks Simon and Nikhil

The discussion on this post has been closed. Please use my contact form to provide comments.