Michael Aird

Possibly. That might work for individuals who are willing to do their own builds but given this project has essentially been "done" for several years, I think it's unlikely that...

@scottdurow Let's take this offline. Email me at michael at campbrain.com and I can give you some pointers.

@nikhilk i had a look at that code you referenced and i think i sort of get it but i'm not entirely sure how to do the "transform" on the...

Hmmm. I wasn't using the [ScriptNamespace] attribute before and everything compiled (and worked) properly with no complaints. In the new module paradigm, it might make more sense to split things...

I believe the published Script.jQuery nuget package only supports jQuery up to version ~1.10 which i don't believe had support for the Promises/A+ specification. Since Script# is no longer actively...

Could I add on to this and request that the [PreserveCase] attribute be allowed at the class level? Or even better at the assembly level?

My understanding is that 1.{current} and 2.{current} should have identical api's but 2.{current} has a bunch of code removed that was required to support older browsers. I'll try to spend...

I agree. Although Script# has been invaluable at getting us where we are today in our project, i'm considering abandoning it in favour of TypeScript due to the extremely slow...

I'm hesitant to add the cultures/selectors as named value enums. the plugin seems to include each culture as a separate file and it's up to the user to include the...

I didn't realize there was similar functionality built into script#. Now that I look at mscorlib, I see the InvariantCulture. maybe it makes more sense for me to work on...