------------------------------------ Microsoft Active Server Pages Beta 2 Release Notes ------------------------------------ Copyright Microsoft Corporation, 1996 Contents: 1. Installation Issues 2. Where is the Product Documentation? 3. Object and Component Notes 4. Known Issues 5. Using a Text Editor with ASP Files 6. Notes for Windows 95 7. Notes for Alpha and PowerPC 8. Server-Side Includes Syntax ------------------------------------------------- Active Server Pages is a feature of the following Web server releases: * Microsoft(R) Internet Information Server 3.0 on Windows NT(R) Server version 4.0 * Microsoft Peer Web Services 3.0 on Windows NT Workstation version 4.0 * Microsoft Personal Web Server on Windows(R) 95 ================================= 1. Installation Issues ================================= Installing JavaVM ------------------------ To install and use the JavaVM included with Active Server Pages, you must first install Microsoft(R) Internet Explorer version 3.0 or later on your computer. If you install JavaVM before Internet Explorer is installed, you will see the following message the next time you restart your computer: OleMainThreadWndName regsrv32.exe entry point not found URLDownloadToCacheFileW not in urlmon.dll Cannot upgrade ASP while Event Viewer is open ----------------------------------------------------------------- You cannot upgrade Active Server Pages while the Windows NT Event Viewer is open. You will see the following error message: "The requested operation cannot be performed on a file with a user mapped section open." Close the Event Viewer and try installing Active Server Pages again. Install Peer Web Services before Active Server Pages --------------------------------------------------------------------- If you intend to use Active Server Pages with Peer Web Services (PWS), be sure to install Peer Web Services before installing ASP. Active Server Pages uses a newer version of ODBC; installing PWS after installing Active Server Pages will write over the Odbcint.dll and Odbccp32.dll files with older versions. If you get an error message about an ODBC conflict, reinstall Active Server Pages to install the newer ODBC files. For important information about using ASP on Peer Web Services, see "Notes for Windows 95 and Peer Web Services". Install Internet Explorer 3.0 on Windows 95 --------------------------------------------------------- Active Server Pages on Windows 95 requires Internet Explorer version 3.0. ===================================== 2. Where is the Product Documentation? ===================================== The Active Server Pages documentation is in HTML format and is installed with the product. After you have installed Active Server Pages, you can view the documentation by choosing Active Server Pages Roadmap from your Web server's program group. From the Roadmap you can also view the Adventure Works sample Web site, which demonstrates many of the features of Active Server Pages scripting and is an excellent source of sample code. You can also view the Roadmap by typing the following address: http:///iasdocs/aspdocs/roadmap.htm. The documentation Roadmap requires either Internet Explorer version 3.0 or later or a browser that supports frames. You will get the best results with Internet Explorer. When you browse the Roadmap using Internet Explorer, you may see a message that the page you are viewing contains potentially unsafe active content. This message is caused by the ActiveX control used to provide the table of contents. To view the table of contents: 1. From the View menu, choose Options, then click the Security tab. 2. Click Safety Level, then click either the Medium or None safety level. This problem will be fixed in the final release of the documentation. ===================================== 3. Object and Component Notes ===================================== The following methods and properties have not been implemented for this release. ActiveX Server Components ------------------------------------- Content Linking Component NextLink.GetNextURL, NextLink.GetPreviousURL, NextLink.GetNextDescription, NextLink.GetPreviousDescription, and NextLink.GetListIndex are not yet implemented for fully qualified URLs. ================================= 4. Known Issues ================================= Setting CacheExtensions Registry Entry to 0 Stops Server -------------------------------------------------------------------------- Setting the CacheExtensions registry entry to 0 will cause your Web server to stop responding when Active Server Pages is unloaded from memory. Running Out of Virtual Memory ------------------------------------------ Under heavy loads, an ASP-based application might run out of virtual memory because memory becomes fragmented over time as Active Server Pages allocates and deallocates memory. To correct this problem, adjust the value of the MemFreeFactor registry entry for your site. The default value is 50%. A value of 0 will increase virtual memory fragmentation but allow other applications to use more memory. A value of 100 decreases virtual memory fragmentation but prevents other applications from using more memory. Thus, if your server is used entirely for ASP-based applications, setting the value to 100 will produce the best results. Updating a File Included by Global.asa -------------------------------------------------- Updating a file that is included by Global.asa does not restart sessions. Therefore, objects stored in the Application object are not reset. To restart sessions, save the Global.asa file. VBScript Line Continuation Character ------------------------------------------------- You cannot use the VBScript line continuation character (_) within an <%= expression%>. For example, the following script directive will generate a VBScript compilation error: <%= "Variable1" & _ "Variable2" %> To work around this problem, you can use the Response.Write method: <% Response.Write("Variable1" & _ "Variable2") %> Registering Components -------------------------------- If you have trouble registering components on Windows NT Server and Windows NT Workstation, you may be using the wrong version of Regsvr32. Please use the version installed by default in the directory c:\Winnt\System32\Inetsrv\Denali\Cmpnts. Using OnStartPage in Server Components -------------------------------------------------------- If you have written an ActiveX server component that uses OnStartPage, you must recompile the component using the header file shipped with the Beta 2 release of Active Server Pages. The header file is in \\ASP\Cmpnts\Asptlb.h. On Windows NT Server and Windows NT Workstation, the default installation directory is \winnt\system32\Inetsrv. On Windows 95, the default installation directory is \Program Files\WebSvr\System. Creating Single-threaded Components --------------------------------------------------- Objects that are marked as single threaded or free threaded cannot access the scripting context inside OnStartPage. Objects marked as apartment threaded or marked as both apartment threaded and single threaded are OK. This will be fixed for the final version of Active Server Pages. Providing Unknown Scripting Language Causes Error ----------------------------------------------------------------------- Specifying an unknown scripting language as the value of the DefaultScriptLanguage registry entry may cause the following error message: http/1.0 500 server error If you get this error, check the DefaultScriptLanguage registry entry. Make sure that you have supplied a valid language. Starting and Stopping Web Services ----------------------------------------------- Your Web server may erroneously report that a service could not be stopped when the Active Server Pages DLL is unloaded from memory. Using Microsoft JScript ------------------------------- To use JavaScript in your ASP files, use "JScript" as the language attribute of the