How to remove Microsoft Java Virtual Machine dependency in Microsoft Remote Scripting

Introduction

This article contains comprehensive instructions and sample source code for an ActiveX control that replaces the Java Applet that is found in Remote Scripting. The control is intended as a short-term solution while customers migrate their code base to alternative technologies like the Microsoft .NET Framework. The Remote Scripting ActiveX Control (RSAx) is an update for the original Remote Scripting 1.0b product. RSAx removes the Microsoft Java Virtual Machine dependency of Web applications that require remote scripting. RSAx replaces the client-side Java applet with an ActiveX control that provides the same functionality. RSAx is intended to be a workaround solution until you can modify your program to use a recommended migration to remove Microsoft Java Virtual Machine dependencies.

Requirements

This article assumes that you are familiar with the following topics:

• Using Microsoft Remote Scripting to call server-side methods and functions from a client-side script.
• Using Microsoft Visual Studio .NET to compile the obtained source code.

Download the remote ActiveX control source code

The source code for the Remote Scripting ActiveX control is available for download. The following file is available for download from the Microsoft Download Center:


Download the RScript.exe package now.

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Build and run the source code

1. Download the source code (Rscript.exe).
2. Extract the contents of the Rscript.exe file to the C:\RemoteScripting folder.
3. Click Start, point to Microsoft Visual Studio .NET 2002 (or Microsoft Visual Studio .NET 2003), point to Visual Studio .NET Tools, and then click Visual Studio .NET Command Prompt.
   
   Note Visual Studio .NET must be installed on your computer to compile the solution.
4. At the command prompt, change the directory to C:\RemoteScripting. To do this, type the following command:
   cd \RemoteScripting
5. Run the Makeall.bat file by typing makeall at the command prompt.
   
   Note The rscriptSetup.msi file is created in the C:\RemoteScripting\rscriptSetup\Release folder.
6. Locate the C:\RemoteScripting\rscriptSetup\Release folder.
7. Copy the rscriptSetup.msi file to the Web server that contains the original installation of Remote Scripting 1.0b.
8. On the Web server, double-click the rscriptSetup.msi file.
9. In the Welcome to the ActiveX Remote Scripting Setup Wizard dialog box, click Next.
10. In the Select Installation Folder dialog box, type the location where the original Remote Scripting 1.0b is installed, click Everyone, and then click Next.
11. In the Confirm Installation dialog box, click Next.
12. In the Installation Complete dialog box, click Close.

Obtain a digital certificate

To sign your control, you must obtain a certificate from a certification authority such as VeriSign. To obtain a digital certificate, visit the following Web site: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

The following are the two classes of Digital IDs for Microsoft Authenticode technology:

• Class 2 certificates are for individuals who publish software that costs US$20 per year. VeriSign requires you to provide your name, your address, your e-mail address, your date of birth, and your Social Security Number. After VeriSign verifies this information, you will be issued a certificate.
• Class 3 certificates are for commercial software publishers. These certificates cost US$400 per year and require a Dun and Bradstreet rating and a company name, a location, and contacts.

Sign the ActiveX control

After you receive the certificate, use the Signcode.exe utility that is included with the ActiveX software development kit (SDK) to sign your code. You must re-sign code if you modify it (for example, to mark the code safer for initializing and for scripting). Signatures are only checked when the control is first installed and not every time Microsoft Internet Explorer uses the control. After your code is signed, even users whose security setting is High will be able to download, install, and register your controls. You can only use pages that initialize and then script these signed controls if you mark them as safe for initializing and safe for scripting. Companies must have one certificate and one group responsible for signing code so that they have control over what is signed.

Deploy the updates

• If your environment permits you to deploy and then install ActiveX Controls, deployment will be handled through standard ActiveX functionality.
• Microsoft recommends that you sign your ActiveX Control for your organization.
• If your environment does not permit deployment of ActiveX Controls, you must deploy and then install the ActiveX control by using a client deployment tool such as Systems Management Server (SMS).
• RSAx uses the WinINet API in Internet Explorer. Therefore, you must compile the Rscript.dll library to depend on a version of WinINet that will be compatible with the version of Internet Explorer that you have deployed in your organization.