MSDN Library Visual Studio 6.

0 Readme

file:///C:/Program Files/Microsoft Visual Studio/READMED...

MSDN Library Visual Studio 6.0 Readme
© 1998 Microsoft Corporation. All rights reserved. Other product and company names herein may be the trademarks of their respective owners. The MSDN™ Library Visual Studio™ 6.0 Readme includes updated information for the documentation provided with the Microsoft® Visual Studio development system for the Windows® operating system and the Internet. The information in this document is more up-to-date than the information in MSDN Library Help. Many of the issues outlined in this document will be corrected in upcoming releases. For general installation issues for the Visual Studio 6.0 suite of products, including side-by-side product installation, see the Installation Notes readme (install.htm).

Contents — Click any of the items below
What's New for This Release

New MSDN Viewer
Setup Issues

Important: This section contains vital information about installing the MSDN Library Visual Studio 6.0 release. Please read all items carefully before you begin your installation. Setup general information Typical, Full, and Custom installation options MSDN setup on a network server "Internet Explorer Version Check" message during Setup Collection file not found in Windows Terminal Server installation Preferred collection message during Setup Uninstalling this release
Known Issues

Collections — Changing preferred collection Internet Explorer 3.02 limitations Internet Explorer 4.01 issues Index — Index subentries sorted under wrong main entries Locate button is active but doesn't work Navigation arrows disappear Printing — Multi-node printing Content in multiple frames cannot be printed simultaneously Subset issues Search may erroneously return "No Topics Found" Search results in some languages may display extraneous characters URLs that do not connect

1 of 8

02/06/2011 05:47 PM

.MSDN Library Visual Studio 6. For Viewer Help. and Help files that are used by the Visual Studio development products. Setup will copy all MSDN documentation and some sample files to your local hard drive. always use the Add/Remove Programs option from the Control Panel or the Setup program from the CD of the MSDN Library you want to uninstall. the July 1998 MSDN Library and all earlier libraries will coexist with the MSDN Library Visual Studio 6. and Visual Modeler samples are not copied to your local drive in a Full install. Full. You will see the entire Library table of contents. What are these COL. Typical. you will be prompted to insert the MSDN Library CD. contents index files. If you do wish to uninstall any library. and Custom installation options. contents index files. The files 2 of 8 02/06/2011 05:47 PM . If you select items in the table of contents that have not been installed locally. The options provide the ability to move some or most files to your local drive in order to reduce dependency on CD access.0. Setup Issues Setup general information You are not required to uninstall previous versions of the MSDN Library that use InfoViewer 5. You are able to access all documentation and samples regardless of the option selected. CHI. Custom installation allows you to specify local installation of a subset of the MSDN Library. These files include the MSDN Viewer system files. and Help files that are used by the Visual Studio development products. CHW. Setup will copy the minimum set of files to your local hard drive. and CHQ files on my local drive and CD? Finding information on HTML tags Library contents Disc layout Uncompressed samples MSDN Library stop list What's New for This Release New MSDN Viewer The MSDN Library Visual Studio 6. CHM. MSDN. and Custom installation options During Setup you will be asked to choose between Typical. (Visual C++®. Full.0 Readme Changing phone numbers General Information file:///C:/Program Files/Microsoft Visual Studio/READMED.) Files copied also include the MSDN viewer system files. The Typical setup option allows you to run the MSDN Library from the CD. click Help from the MSDN menu bar and then click MSDN Library Help..0 technology. For example. The Full setup option allows you to run the MSDN Library almost exclusively from your local drive.0 is the first Library release that uses the HTML Help viewer technology.

5. if you select Start. MSDN Setup will continue with installation.. Collection file not found in Windows Terminal Server installation MSDN Library Visual Studio 6. 2. 1.com/ie/ to download the latest version. see Internet Explorer 3. If you select No. This should leave the C:\MSDN VS6\CD2 directory empty. you must have DCOM 95 or a later version of DCOM installed on your machine for MSDN to work.0 installation will not work properly using Windows Terminal Server. MSDN Library – Visual Studio 6. Choose No to continue with MSDN setup. Create the following subdirectories: C:\MSDN VS6\CD1 and C:\MSDN VS6\CD2. If you are using Internet Explorer 3. you will then receive an error that the msdn*.exe in C:\MSDN VS6\CD1." You must click OK and manually install Internet Explorer.02 or later of Internet Explorer is required. you need to have version 4. 6. C:\MSDN VS6.01 with Service Pack 1 or later of a released version of Microsoft Internet Explorer installed on your system. Copy the contents of C:\MSDN VS6\CD2\MSDN to C:\MSDN VS6\CD1\MSDN.01 is included on the Visual Studio CD. the "Internet Explorer Version Check" message box may appear if you are installing MSDN independently of the recommended Visual Studio installation process. Delete the C:\MSDN VS6\CD2 directory. DCOM 98 is installed as part of the normal setup of Visual Studio.col file could not be found. you select will be copied to your local hard drive along with the files mentioned in the Typical Setup description. In addition to any product or sample files you choose to copy locally. Microsoft Developer Network. 4. For more information. 3. If you choose not to install the recommended version of Internet Explorer (Internet Explorer 4.microsoft. After installation of MSDN. 7.inf file from C:\MSDN VS6\CD2 to C:\MSDN VS6\CD1." If you select Yes. You will be able to access product documentation without having to access the MSDN Library CD for those files that you select to copy locally. If you select items in the table of contents that have not been installed locally. "Internet Explorer Version Check" message during Setup In order for the MSDN Library to function properly. For example. you may need to install NT Service Pack 3.microsoft. Workaround 3 of 8 02/06/2011 05:47 PM . Internet Explorer 4. (Note: If you are using Windows NT 4.0. "Choose Yes to stop setup and install a later version of Internet Explorer..0 product. "MSDN Setup was not completed successfully. You will see the entire Library table of contents. For your convenience. This interactive message will appear if you are using a version of Internet Explorer that is older than the version distributed with the Visual Studio 6.exe to install. Note that version 3. Create a directory on your network drive. The message reads (in part).02 on Windows 95. MSDN will work with reduced functionality. you must then restart MSDN Setup and continue installation.0 Readme file:///C:/Program Files/Microsoft Visual Studio/READMED. you can connect to http://www.02 limitations. During Setup.) If you have chosen to install a later version of Internet Explorer. 8. Or. Check http://www. Copy the Msdn332. Install MSDN on the network by double-clicking setup. MSDN Setup will halt and display a dialog box reading. MSDN setup on a network server You can set up MSDN on a network server by copying CD1 and CD2 to a common network directory.01 with Service Pack 1). select the Full-Text Search Index to search your product's documentation without need to access the MSDN Library CD. Copy the contents of CD1 and CD2 to their respective directories in C:\MSDN VS6 that you just created. Run ie4setup. you will be prompted to insert the MSDN Library CD.0.MSDN Library Visual Studio 6.com/ie/ for more details.

. Internet Explorer 3.0 is set as the preferred document collection for F1 help and general documentation help.0 Readme file:///C:/Program Files/Microsoft Visual Studio/READMED. see the topic Collections — Changing preferred collection. will not display. such as the content included in MSDN. If an additional developer documentation collection is installed.0' collection you are installing. Note: Changing Internet Options for MSDN also changes Internet Options for Internet Explorer. Preferred collection message during Setup You may encounter the following message at the completion of MSDN installation: "MSDN Setup is going to set the preferred developer shell's F1 Help Collection to the 'MSDN Library . If you change the preferred collection while MSDN is open. The preferred collection can be changed in the Visual J++™/Visual InterDev™ Integrated Development Environment (IDE) or in Visual C++ through Tools. Options.02. Options.. You should always close the MSDN window before changing the preferred Visual Studio document collection.dat file from the Windows\Help directory to the specific user profile Help directory. click the Security tab. Help System. Text is not highlighted after a full-text search Highlighting of results from a full-text search is not supported by Internet Explorer 3.0. run Add/Remove Programs from the Control Panel. 4 of 8 02/06/2011 05:47 PM . If you select No. select MSDN Library Visual Studio 6.02 limitations Contents are not displayed in the right pane of the MSDN Viewer If you are using Internet Explorer 3. and then click Disable Ratings. Selected text will not print Printing selected text from an MSDN page is not supported by Internet Explorer 3. F1 Help from Microsoft developer products will route to the previous default collection. Select the Remove All button. . . you may wish to designate that collection as the preferred collection for F1 help and general documentation help. Do you want MSDN Setup to do this?" If you select Yes. click View. your change is not saved.02. During Visual Studio installation.. To view MSDN contents. Uninstalling this release To remove MSDN Library from your machine. and click Add/Remove.Visual Studio 6. Known Issues Collections — Changing preferred collection MSDN Library Visual Studio 6. unrated content. For more information regarding changing collections. F1 Help from Microsoft developer products will be routed to the newly installed MSDN Library. the MSDN Library Visual Studio 6.0 is the help and documentation set for all the Visual Studio products.02 and Content Advisor is enabled. You can get MSDN to work properly by moving the hhcolreg.MSDN Library Visual Studio 6. The user profile directory can be found in the Windows\Profiles directory.

some MSDN links will not work. These topics disable navigation arrows. To change your security settings. View the sample code source.. Note: Changing Internet Options for MSDN also changes Internet Options for Internet Explorer.0 Readme Internet Explorer 4. copy the entire code sample. You will need to navigate to a next or previous topic by clicking on a new topic in the table of contents. even though it appears active. the Locate button does not work. do one of the following: Manually edit the line breaks after you copy the code. Sample code sometimes does not cut and paste properly Line breaks and formatting information may not copy correctly when you copy and paste sample code from the MSDN Library Visual Studio documentation to your code editor. To work around this issue. these keywords are authored as follows: data binding ActiveX controls Data Binding key concepts of They will be displayed in the MSDN index as: data binding Data Binding ActiveX controls key concepts of Because Data Binding was sorted in the index after data binding. Navigation arrows disappear Some topics within the MSDN Library are purposely authored as "hidden" from the table of contents. Locate button is active but doesn't work For some topics. especially those found in Visual Basic® documentation. and then delete the unwanted sections from the pasted version. click View. Data Binding contains the index subentries for both keywords. Internet Options. then index subentries for both keywords will be listed under the keyword sorted last in the index. For example.. Text links appear broken and links present security warnings If security settings are set to disable ActiveX® controls and scripting. Printing — Multi-node printing 5 of 8 02/06/2011 05:47 PM .01 issues file:///C:/Program Files/Microsoft Visual Studio/READMED. paste it to your code editor. Index — Index subentries sorted under wrong main entries If two keywords differ only by case and one or more of the keywords contains index subentries. Then set the security level at a less secure level to allow links to work. and then select the proper zone (Intranet Zone would be appropriate for most users). click the Security tab.MSDN Library Visual Studio 6. including the <pre> and </pre> tags.

That document does not contain the following information about how to use subsets to narrow a full-text search: 1. If you make a subsequent search during the same session. 6 of 8 02/06/2011 05:47 PM .0 Readme file:///C:/Program Files/Microsoft Visual Studio/READMED. Topic Not Found page does not include subsets When using subsets. MSDN does not recommend printing multiple book nodes. you will get a "No Topics Found" message. if you attempt to follow a link from one topic that points to a target topic outside the currently active subset.MSDN Library Visual Studio 6. click the name of the subset you want to search. click OK. To avoid this information loss.. You can also clear the session by quitting and restarting the MSDN Library. 2. On the left pane of the online documentation. Search previous results does not work When you use subsets. If your machine does not have the necessary memory. the "No Topics Found" message is immediately displayed instead of a prompt to insert CD2. Content in multiple frames cannot be printed simultaneously If you attempt to print a node in the table of contents that contains other nodes that have HTML "frame"-based content. Defined subsets deleted In some cases. allow the MSDN Library close process to complete before restarting the MSDN Library. you may receive an out-of-system– memory message. Subset issues Using subsets to narrow a full-text search For information about how to create subsets. Workaround Insert CD2 when requested. Choosing to print a node with a large amount of content can require a large amount of system memory and take quite a bit of time to print. Click List Topics to begin your search. 3. full-text searches do not exclude words on the MSDN stop list. Stop list is ignored When you use subsets. the following message will be displayed: "The selected topics must be printed individually. see MSDN Library Help (select Help and click MSDN Library Help from the MSDN menu). you may see the "Topic Not Found" page. Select the Entire Contents subset in order to access that topic. including recently created user-defined subsets.. click the Search tab." You will need to select a book or page at a lower level in order to print the desired topic. the full-text search "Search previous results" feature currently does not work. Search may erroneously return "No Topics Found" After a Typical installation. This page does not tell you that the reason the topic was not found is that it exists outside the current subset. if you conduct a document search without CD2 in the drive and then click the Cancel button. closing and rapidly opening the MSDN Library could result in the loss of some user-defined information. In the Active Subset list. and the search will behave as expected.

some Uniform Resource Locators (URLs) that connected to Web sites at the time of publication may no longer connect.. General Information What are these CHM. MSDN is always working to keep URLs current. click the Contents tab in the navigation pane of the MSDN Library to open the table of contents. please email msdn@microsoft. URLs that do not connect Because of the volatile nature of the Web.MSDN Library Visual Studio 6.COL file defines the table of contents of a defined document set. primarily those with bi-directional script. or punctuation marks. and CHQ files are index files created to enhance index. The . MSDN is always working to keep phone numbers up-to-date. If you would like to report a problem link.. CHW. The CHI. only the display of the results is affected. and full-text search performance with the MSDN Viewer. Finding information on HTML tags HTML tag information has moved and is not included in the keyword index and cannot be accessed through F1 lookup. keyword. which consists of a number of CHM files. Search results in some languages may display extraneous characters In several languages. This may occur in a search containing wildcards. special characters. Search results will work properly. If you need information on HTML tags.CHM file extension. You can find the reference for HTML Elements inside the Platform SDK folder: » Platform SDK » Internet/Intranet/Extranet Services » Dynamic HTML » DHTML References » HTML References » HTML Elements Library contents 7 of 8 02/06/2011 05:47 PM . CHQ. the search results display may contain extraneous or incorrectly ordered characters. Changing phone numbers Some phone numbers provided in MSDN Library documentation may not be correct.0 Readme file:///C:/Program Files/Microsoft Visual Studio/READMED.com with a description of where the problem link is located. CHI. CHW. and COL files on my local drive and CD? MSDN document files are compiled HTML files that have a .

by. been. and. Disc layout The MSDN Library is included on two CDs." 8 of 8 02/06/2011 05:47 PM . doing. and formatting problems. we. The following words are included on the MSDN Library stop word list: a. with. for.0 Readme file:///C:/Program Files/Microsoft Visual Studio/READMED. then. Documentation. is. You may encounter documentation errors. has. Samples are available for all Visual Studio products within their respective directories. done. I. references to page numbers.chm. the. have. was. Uncompressed samples Samples are located on CD 1 and are uncompressed. at.. here. but. are.com. am. where. those.. see. be. The contents of the MSDN Library will continue to evolve. You can email problems to us at msdn@microsoft. If you enter a search query using a word on the stop list exclusively. We will communicate any errors you report to the appropriate product documentation groups. you. them. dsmsdn. not. these. they. on. saw. and Setup files have been placed on the CDs to maximize content space and to minimize CD swapping. Three document files are located on CD 1: Two files. how. The Microsoft Developer Network team does not edit most of the product documentation. an error is returned: "The syntax of the search query is incorrect. too. can. CD 1 contains Setup and sample files and CD 2 contains document files. samples.chm and dshelp. its. which. being. is used to link samples on Disc 1.MSDN Library Visual Studio 6. to. the third file. this. Some samples are available through document links and others are referenced through Visual Studio product documentation on the MSDN Library. could. of. do. there. and articles included in the MSDN Library. or. may. it. MSDN Library stop list A word stop list has been used to reduce the size of the keyword index and increase search performance. as. specifications. that. from. seen. an. she. We have provided product documentation and a substantial portion of the current MSDN Library. vcsample. did. in. are installed locally in any MSDN installation. had. does. very. so. he. when.chm.

Sign up to vote on this title
UsefulNot useful