Redistributable File List Welcome!
Welcome!

Redistributable File List for Microsoft® SDK for Java™, Version 1.5

This document identifies the files that you may redistribute with your application developed using Microsoft SDK for Java 1.5. The conditions under which you may redistribute these files are described in the separate License Agreement under Redistribution Requirements.

The redistributable files are located inside SDK directories, unless otherwise noted. Files will be part of the SDK download and installed on your hard drive. When you redistribute any of these files, you should make sure you are redistributing the correct version of the files.

Categories of Redistributable Files

The following categorization of redistributable files are described in this document.

  1. Microsoft Win32 Java VM Files
  2. Plugin for Navigator© files
  3. SDK tools files
  4. CAB Files
  5. Sample Files
  6. DirectX File
  7. General Redistribution Information

1. Microsoft Win32 Java VM

You can either redistribute IE30Java.exe (self extracting executable) in the SDK \bin directory or redistribute the following binary files that are in \MSJavaVM directory:

msjava.inf

jautoexp.dat

javaDbg.txt

javaEE.dll

javasntx.dll

setdebug.exe

regsvr32.exe

jit.dll

javaprxy.dll

jdbgmgr.exe

msjava.dll

msawt.dll

vmhelper.dll

javart.dll

jview.exe

wjview.exe

mfc40.dll

msvcrt40.dll

classr.exe

classd.exe

javasup.vxd

For current information on how to redistribute the latest version of Win32 Java VM, see our web site: http://www.microsoft.com/java/

2. Plugin for Navigator Files

These files are provided with the SDK in the \NSPlugIn Support directory:

npmsjava.dll: Microsoft VM for Java plugin to be used with Navigator

npmsjava.htm: Information on how to use the plugin with Navigator.

3. Tool Files

These files are provided with SDK in the \bin directory except Native.h and Nativecom.h are in the \include directory (note Java compiler(jvc.exe), and pre-release version of Script Debugger for IE are not for redistribution):

JView.exe: Java application viewer with internationalization enabled

AppletViewer.exe: Java applet viewer with internationalization enabled

JExegen.exe: A tool to convert stand alone Java applications into a Windows executable (.EXE)

JavaReg.exe: A Java/COM registration utility

JavaTLB: A tool for generating Java classes from a variety of type libraries

Msjavah.exe: Microsoft version of C header file generator

Native.h: Header file for writing raw native code interface

Nativecom.h: Header file exposes public COM APIs used by the VM

4. CAB Files

cabarc.exe: A utility that creates, extracts, and lists the contents of cabinet (CAB) files, containing multiple files.

master.inf: A template for the .inf file included in the CAB file and used by Internet Explorer when unpacking libraries.

5. Sample Code Files

The following sample folders are located in the \samples directory:

AWT

Debugger

DirectX

Scripting

JExegen

JView

Native

Native_com

Native_raw

Script Debugger

Version

6. DirectX File

The following file is required for redistribution if developer intend to use beta version of DirectX class library extensions, it is located in SDK \DirectX2\direct directory:

Direct.dll

7. General Redistribution Information

Version Checking of Redistributable Files

Because other applications may redistribute earlier or later versions of the same files as redistributed with your application, it is important that you install newer versions of the files on top of older versions on your user's system, but not older versions on top of new versions. Typically, version checking is the responsibility of your setup program. If you do not have a setup program for your main application, then you must accomplish the version checking manually when installing the redistributable files on your user's system.

The programmatic technique for version checking varies, depending on which category of file you are redistributing. In each of the following sections, the version checking technique is described for each category of files. Briefly, the version checking techniques are as follows:

For the DLLs, use the standard version checking APIs available as a standard part of the Win32 API. The Win32 version checking APIs are beyond the scope of this article. For the Class library files, see sample Version, SDK has provided ClassR.exe in the \MsJavaVm directory for version checking as well.



Top© 1997 Microsoft Corporation. All rights reserved. Legal Notices.
Other product and company names herein may be the trademarks of their respective owners.