JScript.NET Editor?

Question

 

Hi

I hope this is the right place to ask this kind of question:

I use JScript.NET for serve-side scripts.

I noticed that Visual Studio 2008 Beta 2 (and every other Version I assume) doesn't support JScript.NET Syntax or compiling JScript.NET files (I've done this with the console so far)?

Why doesn't VS support JScript.NET? Is there a Plugin to make JScript.NET support possible? Does Microsoft recommend another Editor for JScript.NET development?

 

Thanks

 

 

Best Regards

 

janny

Answer 1

Unfortunately, VS 2008 doesn't support JScript.NET. If you would like to compile JScript.NET files, you need to install .NET SDK 2.0 and use jsc.exe from the command line to compile it. As far as I know, Microsoft has no IDE support for JScript.NET, you could try an eclipse plugin - http://sourceforge.net/projects/jseditor/

 

Answer 2

Hi

Yes that's what I'm saying, MS's IDE Visual Studio doesn't suport JScript.NET, but I can't understand this matter of fact.

I want an IDE which supports JScript.NET syntax, intellisense for JSCript.NET and the possibility to compile and I think Microsoft should provide something like that to establish JScript.NET as an as easy to use language as other .NET languages.

I already thought about using eclipse, is the linked Plug in just an javascript-plugin or does it support JScript.NET as well?

 

Thanks

 

Cheers Janny

 

 

Answer 3

The linked plugin is a javascript-plugin for Eclipse and you can try to see if it supports JScript.NET. 

Answer 4

Hi all

I was also looking for a JScript.NET Editor because I think it's a nice language. But no version of Visual Studio supports it. IMHO it's a shame that Microsoft developed a good IDE and a nice language which is not supported in Visual Studio 2008 either...

Good Luck & Have Fun

Answer 5

Brathering wrote:

I was also looking for a JScript.NET Editor because I think it's a nice language. But no version of Visual Studio supports it. IMHO it's a shame that Microsoft developed a good IDE and a nice language which is not supported in Visual Studio 2008 either...

 

The real (unstated) purpose of JScript.NET is to provide a means to port JScript based ASP to ASP.NET.

 

Where JScript.NET is available C# is also.  For new development I can see no commercial sense in developing in JScript.NET.  In the dynamic language stakes JScript is being eclipsed (pun sorry) by other languages like Python.

 

 

 

 

Answer 6

Anthony Jones wrote:

Where JScript.NET is available C# is also.

Ya okay, but with JScript.NET you can also create Windows applications and do all what is possible with .NET and if there is someone who already knows JScript or JavaScript respectively for this people it is easier to write applications in JScript.NET than leraning a new language like C# instead.

Anthony Jones wrote:

The real (unstated) purpose of JScript.NET is to provide a means to port JScript based ASP to ASP.NET.

In ASP.NET there is C# available also.. .

Answer 7

Brathering wrote:

Ya okay, but with JScript.NET you can also create Windows applications and do all what is possible with .NET and if there is someone who already knows JScript or JavaScript respectively for this people it is easier to write applications in JScript.NET than leraning a new language like C# instead.

 

Are you sure it would be easier.  I doubt it. In order to do Windows Apps in JScript.NET there are quite a large number of concepts new in JScript.NET that aren't in JScript that need to be taken on board first (such as typed variables).  The structure of the code needs to conform more closely to that you'd see in C# and VB which again would be unfamiliar.

 

Then unless you going to do it all from first principles you'll be looking at examples from books or the web.  I'd be very surprised you'll find any examples in JScript.NET of windows apps, if there are they'll be of the "hey, you can even do windows apps in JScirpt.NET" ilke.  So you would either have to decipher the API without the benefit of samples or learn to read C# or VB versions. 

 

By the time you've got a sensible strongly typed JScript.NET windows app built it wouldn't look a great deal different from the C# version and you would in fact have had a steeper learning curve to climb than had you taken the time to learn enough C# to do the same job.  Bear in mind that apart from learning enough C# to be able to read samples written in C# many of the principles that in C# come from the underlying CLR which would apply to JScript.NET anyway.

 

 

 

 

Answer 8

Anthony Jones said:

The real (unstated) purpose of JScript.NET is to provide a means to port JScript based ASP to ASP.NET.

The stated purpose of JScript.NET is that it is a revision of the international standard ECMAScript. Is ASP an international standard? I am not sure, but as far as I know, it is not. Please understand that Windows is not the only operating system. ECMAScript is used in many environments in which ASP is not.

If JScript.NET was intended by Microsoft to provide a means to port JScript based ASP to ASP.NET, then Microsoft would have made JScript.NET easier to use.

---

Sam Hobbs; see my SimpleSamples.Info

Answer 9

Anthony Jones said:

Are you sure it would be easier.  I doubt it. In order to do Windows Apps in JScript.NET there are quite a large number of concepts new in JScript.NET that aren't in JScript that need to be taken on board first (such as typed variables).  The structure of the code needs to conform more closely to that you'd see in C# and VB which again would be unfamiliar.

 

Then unless you going to do it all from first principles you'll be looking at examples from books or the web.  I'd be very surprised you'll find any examples in JScript.NET of windows apps, if there are they'll be of the "hey, you can even do windows apps in JScirpt.NET" ilke.  So you would either have to decipher the API without the benefit of samples or learn to read C# or VB versions. 

 

By the time you've got a sensible strongly typed JScript.NET windows app built it wouldn't look a great deal different from the C# version and you would in fact have had a steeper learning curve to climb than had you taken the time to learn enough C# to do the same job.  Bear in mind that apart from learning enough C# to be able to read samples written in C# many of the principles that in C# come from the underlying CLR which would apply to JScript.NET anyway.Of course it would be easier.

Am I in the correct forum? I thought this is the forum for JScript.Net but I get the impression from the comments above that it is not.

Of course it would be easier for someone familiar with JScript to learn JScript.Net than other languages. If a person is familiar with C# then they would of course prefer to use C# instead of investing the time to learn another language that they are not yet familair with such as VB, C++, Pascal, Perl, Ruby, Python or Java. Of course, many people would say that they are eager to learn a new langauge that they consider to be useful, and that would include the new and improved JScript.

Note that .Net is also an ECMA (international) standard. The standard is not called .Net; it is called CLA or CLI, I forget which one, but otherwise it is a standard. Samples of windows using .Net will be useful for any other language using .Net.

---

Sam Hobbs; see my SimpleSamples.Info

Answer 10

So now that functional languages are popular again, and the C# team had to jump through hoops to add some functional constructs into C# 3, how come JScript.Net isn't more popular? I'd think Microsoft could have cut Adobe AIR off at the needs had they thought to put some focus into JScript.Net. (Jscript.Net +  WPF would beat anything that you can do with Adobe AIR). 

Is JScript.Net dead? There is not even editor support for it in VS2k8 (as this thread discusses). And all the replies seem to be "well, just use C#." 

The SilverLight team went and created their own version of managed JScript instead of reusing JScript.Net.  

My *guess* is that the JScript.Net code base is so old and ugly that no one wanted to touch it anymore. But being able to do:

function blah(i, f)

{

  return f(i);

}

blah(1, function(i){return i + 1;});

in a pure .Net language is pretty powerful. And without all the syntactic overload that C# had to add. 

So... is JScript.Net dead?

Answer 11

I am using VC 6 but I expect to be using VS 2008 soon. For now, I have been attempting to use nmake to compile JScript .Net from within VS. I am not sure if VS 2008 supports namke; perhaps we must use msbuild in VS 2008.

Regardless, is anyone interested in using JScript .Net that way? It won't do the intellisense and such but it should make building (and testing?) easier.

---

Sam Hobbs; see my SimpleSamples.Info