Nikhil Kothari

I am not bought into generating TypeScript ... it adds yet another step, and not sure its worth the additional complexity/indirection for the script# developer. Specifically, I don't see how...

DateTime should probably not be a value type in script# so it correctly reflects script semantics.

I agree that is an interesting scenario ... however script# was never intended to cater to the cross-compilation/porting scenario, though if you tread carefully, you can get a bit lucky...

Change made. https://github.com/nikhilk/scriptsharp/commit/6e8d8059d66e9b1cf6e4c206f2bd7625db04ff43

This should be helpful. I imagine this is a commonly used jQuery plugin. Though one thing to in fact note would be the support for globalization that comes from script#...

On culture names ... here is a sample I saw on their github page: ``` Globalize.culture( "fr" ); ``` I was hoping in script# one could write: ``` Globalize.Culture(Cultures.French); ```...

fr and fr-CA are both valid cultures. fr is the parent of fr-CA (and fr-FR) and is less specific than the other two, and certainly useful where you're not trying...

The general idea behind the preview release is to work out those issues. There isn't any other way they are going to surface without real-world use. Its either put out...

Things should be good between 0.7.5+ versions - since everything is packaged as nuget packages. 0.7.4 used to install scriptsharp.dll to the gac, so I am not completely sure. I...

Did you compile your attribute in a c# project that references the script# mscorlib assembly? In other words, in the script# world, you cannot reference the regular .net mscorlib.dll. Best...