Re: Future JScript .NET Support in Visual Studio and .NET
- From: Gerry Hickman <gerry666uk@xxxxxxxxxxxxxxxx>
- Date: Tue, 21 Nov 2006 00:03:36 +0000
Hi William,
You may be getting mixed up with some of the terminology and dependencies. JScript.NET is not comparable with JavaScript. It's not even comparable to ECMAScript or JScript. Here's a brief summary:
JavaScript was originally a Netscape language, but today it tends to refer to "client-side browser scripting" and can be used the same (for all common operations) in both Mozilla or IE provided you follow the standards.
JScript (without the .NET) is Microsoft's implementation of ECMAScript and has a few Microsoft specific extensions. It's capabilities are similar to VBScript but it's future proof and it's easy to share code blocks for both client and server; it's also the best way to call COM objects from a high level language. It also gives you a route into HTA's and logon scripts that can use standards based code that can run fast and with few dependencies. Imagine how idiotic it would be to have logon scripts that depend on .NET! You can still use JScript with ASP.NET 2.0, but you can't use VBScript.
There's a gray area between JScript and JavaScript in that they can both instantiate objects, but "ActiveX" objects are only compatible with Microsoft systems, so Adobe and Mozilla will have other similar constructs for creating objects, but that does not mean they will be directly compatible.
JScript.NET is a means of making calls to the .NET Framework. It has a syntax a bit like JScript, but then so does C#.
I never understood why Microsoft created JScript.NET or J# in the first place? I don't see any future in them as a means of calling the .NET Framework, the only language I know of that's EMCA approved and works with .NET is C#, they kept VB.NET to keep the beginners happy, but what's the point of the others? It will be interesting to see what it's enhanced and what is "deprecated" when ORCAS is released.
The part where you talk about "turning C# into JavaScript"; it's worth remembering C# is just a language, it's not the .NET Framework, so anyone reading should understand it does NOT mean you can take a C#.NET project and turn it into JavaScript! Two very different things. Yes you could transcode C# and use it for client-side script, but why would anyone do that when JavaScript is already superior for that task?
William Sullivan wrote:
You mean Javascript? I wouldn't hold your breath. Too many different implementations out there to make intellisense worth anything.
In other news, check out Nikhil Kothari's blog (www.nikhilk.net). He has a compiler that takes C# and turns it into Javascript. Wild stuff, but in the early stages, I believe. Also, the Microsoft Ajax team has done some amazing stuff in creating a cross-browser compatible Javascript framework.
"Troy Taft" wrote:
Is Microsoft planning to increase support for JScript .NET in the .NET framework and in Visual Studio .NET?
--
Gerry Hickman (London UK)
.
- Prev by Date: Re: asp.net 2.0 adds unwanted semicolons
- Next by Date: Re: VS2005 and Vista
- Previous by thread: Re: VS2005 and Vista
- Next by thread: Re: Future JScript .NET Support in Visual Studio and .NET
- Index(es):
Relevant Pages
|
