@scriptsharp

As the original c# to JavaScript compiler, Script# lets you write HTML5 and Node.js applications in C# and compile them into plain old JavaScript.

 Redmond, WA
scriptsharp.com
Joined July 2009
  • Tweets379
  • Following0
  • Followers585
Replying to @KDSBest
@KDSBest mostly be selective about dependencies ... restrict yourself to what you have in JavaScript.
1
Replying to @KDSBest
@KDSBest @nikhilk in general, the goal has never been to enable both js and .bet dev from the same source, but possible with care.
Replying to @JasonMacEntee
@JasonMacEntee afaik, current versions of office on web, sharepoint, dynamics, bing maps etc. were built via script#. Also, I think tableau.
1
Replying to @web_bod
@web_bod posted an answer ... hopefully it helps.
1
Mostly a prototype for some backend-as-a-service ideas, this serves as a script# example for authoring a node.js app github.com/nikhilk/simpleclo…

GitHub - nikhilk/simplecloud: Simple script-based cloud backend.

Simple script-based cloud backend. Contribute to nikhilk/simplecloud development by creating an account on GitHub.

github.com
2
3
New import libraries added for your script#-based nodejs apps: restify (thx @theoutlander) and azure. Check em out: github.com/nikhilk/scriptsha…
2
2
@KallDrexx you can use anonymous delegates.
1
If you use script#, please chime in with your thoughts on the topic of import libraries over on github: github.com/nikhilk/scriptsha… ... thanks!

What are the expectations for import scripts on large JS libraries? · Issue #332 · nikhilk/script...

I've been using a few JS libraries that have massive API's like Google Maps, ElasticSearch, and a few others that aren't as huge but fit the problem that I'm about to describe. Whil...

github.com
@NZxRMGuy awesome to hear. Understand. This sort of overhaul was quite overdue. Had to bite the bullet. What are you guys building? Public?
@NZxRMGuy though the AMD pattern is really goodness, and hence I don't make it easy out-of-the-box. :)
@NZxRMGuy now, I can safely say, I did think through how you'd escape the AMD pattern if you wanted to (I did think most of it in advance).
@NZxRMGuy this is mostly a vs intellisense + AMD pattern question. See this gist for an equivalent sample: gist.github.com/4660121
@NZxRMGuy tried sample of AMD style script, intellisense work s fine. Just add module object to a global, since you aren't using require.
@NZxRMGuy see github.com/nikhilk/scriptsha… ... if you don't have an AMD loader, ss.js registers into the global namespace.
@NZxRMGuy (cont'd) i.e. there is no $. On intellisense, how does vs deal with AMD pattern in general? TypeScript requires .d.ts files.
@NZxRMGuy eg (see github.com/nikhilk/scriptsha…) ... "flickr" module with type named "FlickrPhotoService" - accessed as flickr.FlickrPhotoService.
@NZxRMGuy yep, hear you. Hopefully, module pattern is good for future external use. New stuff is nuget based. Side-by-side at least helps.
@NZxRMGuy finally, ss.js is smaller than mscorlib.js as an added benefit.
@NZxRMGuy changes (AMD output + ss.js as a module) gets script closer to modern scripting patterns: more minimizable, and no global impact.
@NZxRMGuy if your base app has mscorlib.js, then it was written with script# as well. That can't be moved to 0.8 as well?
Load more