System.NullReferenceException on Mono (Jurassic removed)

[ArturD]

It seems that Jurassic dependency was removed and SassAndCoffee is no longer compatible with (it uses only ie com objects) mono. Please bring back mono compatibility (with Jurassic, Jint whatever).

error:
System.NullReferenceException: Object reference not set to an instance of an object
at SassAndCoffee.JavaScript.IEJavaScriptRuntime.Initialize () [0x00000] in :0
at SassAndCoffee.JavaScript.JavaScriptCompilerBase.Initialize () [0x00000] in :0
at SassAndCoffee.JavaScript.JavaScriptCompilerBase.Compile (System.String source, System.Object[] args) [0x00000] in :0
at SassAndCoffee.JavaScript.JavaScriptCompilerContentTransformBase.Execute (SassAndCoffee.Core.ContentTransformState state, System.Object[] args) [0x00000] in :0
at SassAndCoffee.JavaScript.CoffeeScript.CoffeeScriptCompilerContentTransform.Execute (SassAndCoffee.Core.ContentTransformState state) [0x00000] in :0
at SassAndCoffee.Core.ContentPipeline.ProcessRequest (System.String physicalPath) [0x00000] in :0
at SassAndCoffee.AspNet.PipelineHandler.ProcessRequest (System.Web.HttpContext context) [0x00000] in :0
at System.Web.HttpApplication+c__Iterator6.MoveNext () [0x00000] in :0
at System.Web.HttpApplication.Tick () [0x00000] in :0

[kogir]

In many cases Jurassic was slow enough as to be useless. If you still wish to use it, simply implement an IJavaScriptRuntime for it.

I don't really have time right now to do it myself, sorry.

[ArturD]

Hi,

Slow is better than nothing.
Is performance the only reason to remove Jurassic ?
Wouldn't caching solve problem ?
If I wrote a patch with Jurassic and some simple cache, would you consider
merging it to 2.1 ?

2012/4/16 Nick Sivo <
[email protected]

In many cases Jurassic was slow enough as to be useless. If you still
wish to use it, simply implement an IJavaScriptRuntime
for it.

I don't really have time right now to do it myself, sorry.

---

Reply to this email directly or view it on GitHub:
#52 (comment)

[kogir]

Sure - I'd like to bring mono support back. My 2.1 branch is kind of a disaster, so you might want to target it against trunk instead.