Managed JScript Limitations...
Managed JScript implementation, on Silverlight is a full implementation of Javascript Ecmascript 3.0 version. This supports interop with all other .NET languages and also other dynamic languages.
But other day, someone asked me about what doesn't work yet there. So could get the following from the silverlight site, where it talks about How to: Program Silverlight with Dynamic Languages
In the Silverlight 1.1 Alpha release, Managed JScript has the following limitations:
- The mapping between .NET Framework objects and Managed JScript objects is currently limited. For example, the Managed JScript String object cannot be used in places where System.String is expected, but the string primitive can be used. Managed JScript arrays cannot be used where .NET Framework arrays are expected.
- There is limited support for Javascript-style enumeration (that is, listing names instead of values); it is supported only for objects that implement IList and IDictionary. Enumeration on other .NET Framework objects lists values instead of names.
- Generics are not yet supported.
- Method overload resolution for candidate methods with numeric types other than double is not yet supported.
- Exceptions thrown in event handlers that are hooked up from Managed JScript code are not logged at the top of the HTML. Exceptions that are hooked up in markup are logged.
- The Eval function does not produce a correct value unless its input is a sequence of statements ending in a simple expression statement.
- The arguments.callee property is not supported.
Will try to keep this list up to date , as and when things gets added or removed from here.
