locked
Where to get Jscript.net ? RRS feed

  • Question

  • User1902984708 posted
    I have just discovered that have no Microsoft.JScript namespace in my Visual Basic.Net 2002 dev. env. Is Micosoft.JScript not part of the default .net framework ? Do I need an adult dev. env. like Visual Studio.Net 2003 ? Where can I download it (I do not want to purchase VS.net 2003) ? Yours, Patrick
    Thursday, April 22, 2004 12:42 PM

All replies

  • User1025213086 posted
    JScript is part of the .NET Framework, but you may have the 1.0 version installed, try installing the v1.1 or the v1.1 .NET Framework SDK. If you plan to use the JScript.NET engine as part of your project, download the Shared Source CLI at http://msdn.microsoft.com/library/en-us/Dndotnet/html/mssharsourcecli.asp?frame=true as it has the compiler and engine source their.
    Thursday, April 22, 2004 8:58 PM
  • User1902984708 posted
    In fact, I want to include Jscript's Eval function in my VB project as described in the featured article of last Saturday (Using JScript.NET And Eval For Dynamic Execution From C#) Do I need the Shared Source CLI for this ? Can I expect that my app will run on my Internet site if my provider has installed the plain vanilla .net framework 1.1, or do I need to include sth. special in my project when uploading it to my provider ? Yours, Patrick P.S. The article that I mentioned can be found at: http://www.odetocode.com/Code/80.aspx
    Friday, April 23, 2004 4:03 AM
  • User1902984708 posted
    I quickly threw an exception in my app and got the following version info: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573 If JScript.Net is part of v1.1, then VS.Net 2002 my not reference it.
    Friday, April 23, 2004 4:20 AM
  • User1025213086 posted
    I don't think that might happen, the difference between v1.0 and v.1.1 aren't that major, except for a few things changed here and there, it should work, but if it doesn't, get the Shared Source CLI, rebuild the JScript.NET engine without any changes and use that assembly to reference JScript in your project. I hope that works.
    Friday, April 23, 2004 7:51 AM
  • User1902984708 posted
    I want to shared me valuable experience with you: I referenced Microsoft.JScript 1.1 in VB.net 2002 which forced me to reinstall VB.Net. Why ? When you reference a Microsoft.* namespace from a certain framework version, you force VB.Net 2002 to load all other basic namespaces (like System) from the same framework version. But v1.1. is incompatible with VB.Net 2002. Web forms compile fine, but the Designer can't build them anymore. And to show me that I was very stupid today, a nice v1.0 Microsoft.JScript appeared after the reinstall (which was surely their before reinstall ...) Anyway, it can be nicely referenced in VB.Net 2002. Now I have a nice eval function in VB.Net. A stupid guy had a stupid day. As if I hadn't anything else to do ... Thanks for your help anyway. I will for sure have a look at the Shared Source CLI, only to die less stupid ... Patrick
    Friday, April 23, 2004 8:19 PM
  • User1025213086 posted
    um, sorry to put you through that, I don't use VB.NET so I didn't know. my apologies for your inconvenience.
    Saturday, April 24, 2004 8:46 AM