ID: Q167837
The information in this article applies to:
The following article contains the complete contents of the Readme.txt file distributed with the Internet Client SDK version 4.0. (This is the Readme.txt installed on the \InetSDK folder.)
Release notes for the Internet Client Software Development Kit
Copyright (c) Microsoft Corporation, 1997
NOTE: If you did not access this document from <your SDK folder>\help\default.htm, go to that location because it is a better place to begin reading documentation.
This Readme.txt is the second URL in that document's left-hand frame. If you are unfamiliar with the Internet Client SDK, you might want to look at the Overview section. There is a great deal of new material and technologies available through that section.
WELCOME TO THE INTERNET CLIENT SDK
These are the release notes for the Internet Explorer 4.0 version of the SDK. This release has been tested primarily on Visual C++ 5.0, Windows 95 and Windows NT, and Internet Explorer 4.0 releases.
Here's a brief description of the contents of this folder, followed by release notes:
BIN SDK tools, DLLs, and self-extracting .exe files
HELP HTML documentation (Default.htm) for Web content and software
development
INCLUDE Include files for Internet development
LIB Libraries for Internet development
SAMPLES Samples for Web content developers and software developers
COMPLIB Internet components (ActiveX Controls, Java applets, and so
on)
To do development with this SDK, you need to have installed on your computer:
INSTALLATION ISSUES -- CD AND INTERNET INSTALLS
ActiveSetup from the Internet:
Essentially the ActiveSetup from a CD is identical to the ActiveSetup from the Web. One difference is that the CD will have an image of a fully installed SDK. If for some reason you are unable to use ActiveSetup, this should not prevent you from being able to use the documentation and seeing the samples. Copying those files from the CD to your hard drive (without using ActiveSetup) is not a supported method of installation.
The new Web site for installing the SDK is: http://www.microsoft.com/msdn/sdk/inetsdk/ASetup/
The download site is designed to allow you to download the bits that you're interested in, while ignoring the others for another day. You can return to the site for incremental downloads that nicely integrate into your installation. The downloads are targeted at three major development tasks/audiences: Web and Desktop Content Providers, ActiveX Component Developers, and Internet Application Developers. There is also a Component Library with helpful Internet components such as the Microsoft Chat and NetShow controls. A useful feature of the documentation is that it integrates well on the client computer. If you make a jump from the documentation to a set that you have not yet installed, the documentation will invite you back to the download site to install that documentation set. When you do this, the links will be resolved to the new pages.
GETTING STARTED ON DOCUMENTATION
The documentation has lots of great new content. The entry point is <your sdk dir.>\help\default.htm. All documentation should be accessed through this file. Accessing other HTML files directly will cause scripting errors and break navigation links.
CONFIGURATION ISSUES
If you have Visual C++ 5.0 and the latest release of the Platform SDK, you should set your environment variables by executing the following commands on your command line (note: make exceptions to make sure you go to the correct directories):
cd \vc\bin
vcvars32 x86
cd c:\mstools
setenv c:\mstools
cd c:\inetsdk
setenv c:\inetsdk
cd \vc\bin
vcvars32 x86
cd c:\inetsdk
setenv c:\inetsdk
If you are developing on a Windows 95 computer, you will want to increase your environment space. You can do this by changing "Initial environment" on the "Memory" tab of the "Properties" menu, which is accessible by clicking in the extreme upper-left corner of your MS-DOS prompt window.
BUILDING/USING SAMPLES
For both software and content developers, the samples are located in the \samples directory, and are often referenced in the documentation as examples. The Samples.htm file (accessible from Default.htm) provides more detailed information about each sample.
You will find several new samples targeted at content development. These are not the traditional type of samples that use compilers or linkers-- these are HTML and CDF samples, and others, that show you how to use or develop content on Web pages.
For software developers, each sample that produces a binary has a makefile in its directory. You can execute all of these recursively by executing ...\samples\makeall.bat. All samples should build on Visual C++ 5.0.
Several of the ChatOCX samples are Visual Basic samples. You will need to have Visual Basic installed to build and execute these samples.
WHAT'S IN THE \BIN DIRECTORY
Lots of new, good stuff!
Many of the following are self-extracting CAB files; you can read more about them in the documentation or in the .txt files in the \bin directory. Upon download, these file are installed in either the \bin directory of the \complib directory.
MSTASK.H:
The Task Scheduler interface introduced during beta as ISchedulingAgent has been renamed to ITaskScheduler in the final release of the product. This is FYI only, no recompile is necessary.
BLEND TRANSITION - CSS:
Attempting to assign a shape value (for example, Box-In, Wipe-Left) in a script to a Blend transition causes Internet Explorer to GPF. Don't do this. Setting a shape value to a Blend Transition in CSS is ignored.
This will most likely happen when authors are editing code that changes a Reveal Transition to a Blend Transition without taking out any code that sets the transition shape.
BINDINFO and ATL:
The BINDINFO structure has changed size between Internet Explorer 3.x and Internet Explorer 4.0. There are more details in the documentation for BINDINFO that tells how to check this structure and how it applies to your code.
Some of the ATL samples in this SDK--Glass, IEMime, and TDC for example-- use classes based on the ATL CBindStatusCallback class, which implements asynchronous moniker downloads. The version of ATL shipping with Visual C++ 5.0 fails to release some interfaces and handles the size of the BINDINFO structure incorrectly inside CBindStatusCallback. The Glass IEMime and TDC samples are not affected because they provide their own revised CBindStatusCallback implementations. However, any customers who create projects based on these SDK samples but use CBindStatusCallback directly should be aware of these issues. ATL users should also be aware. Microsoft is currently planning to resolve these problems in a future Service Pack for Visual Studio.
OBJBASE.H
CoCreateStandardMalloc is defined in the Objbase.h header file, however this function is obsolete and will be removed in a future release. Attempting to use this in your code will generate unresolved symbol errors during linking. CoGetMalloc should be used instead.
LATE BREAKING DOCUMENTATION UPDATES
AUTHENTICODE RELEASE NOTES:
The following functionality has been added to the CertMgr program.
Putting Certificates, CTLs, and CRLs with CertMgr
The following syntax can be used to invoke CertMgr to put an X509 encoded certificate, CTL, or CRL into a file:
CertMgr -put [options] [-s [-r registryLocation]] SourceStore FileName
CertMgr can put either certificates, CTLs, or CRLs. If there is more than one item in one of these categories, the user has two options:
1. Use the -n and -sha1 options to uniquely identify the item.
2. Do not specify any options, and CertMgr will prompt the user with a list
of items to put. The user responds by entering the index of the item to
add.
The options are:
-c Put certificates.
-CTL Put CTLs.
-CRL Put CRLs.
-7 Save the certificate, CRL, or CTL as a PKCS#7.
-e encodingType Certificate encoding type.
-y storeProviderType Store provider type.
-f dwFlags Store open flag. This is the dwFlags parameter
passed to CertOpenStore. The default value is
CERT_SYSTEM_STORE_CURRENT_USER. Meaningful only
if -y is set. For more information see the
CryptoAPI 2.0 documentation.
-n commonNameString The common name of the certificate to
put. Can be used only with certificates.
-s Indicates the SourceStore is a system store. If
this option is not set, the store is a
StoreFile.
-sha1 sha1Hash The SHA1 hash of the certificate, CTL, or CRL to
add.
-r registryLocation Identifies the registry location of the system
certificate store. Meaningful only when -s is
set. Must be set to either currentUser or
localMachine. CurrentUser is the default.
currentUser means that the certificate store is
under the registry key HKEY_CURRENT_USER,
localMachine means HKEY_LOCAL_MACHINE.
-? Displays all the options.
The following example puts an X509 encoded certificate, that is located
in the Root certificate store, to a file called newCert.cer. The
certificate's common name is "myCert".
certmgr -put -c -n myCert -s root newCert.cer
<img id=sample src="sample.jpg" style="filter:blur(amount=2)
flipv()">
should be:
<img id=sample src="sample.jpg" style="filter:blur(strength=2)
flipv()">
Keywords : kbreadme AXSDKMisc
Version : WINDOWS:4.0
Platform : WINDOWS
Issue type : kbinfoLast Reviewed: July 29, 1998