NIM033755 for No Product Found

Numéro d’ID de bogue	NIM033755
Envoi	March 31, 2008
Dernière modification	June 5, 2024
S’applique à	No Product Found
Version trouvée	9.3
Statut	Will Not Be Addressed

Informations supplémentaires

No Public Explanation

Solution de contournement

don1760 - 3/25/08I found that if you change the order of how documents are loaded for Help content in the Document Explorer that the correct ESRI type can be found using F1 help for <a href="http://VB.NET" target="_blank">VB.NET</a>. To accomolish this:1. In Visual Studio (2005 or 2008) hit F1 on an ArcObject Type to open the Document Explorer.2. In the Document Explorer, choose Tools | Options from the menus.3. In the Options dialog, expand the 'Help' node and click on the 'Online' sub-node.4. In the Options dialog, in the 'When loading Help content' area change the radio button to 'Try online first, then local' and click OK to close the dialog.Repeat step 1 and this time the F1 help will take directly to the ESRI Type.Note: this is only a workaround. The underlying problem is still not fixed. Somehow the <a href="http://VB.NET" target="_blank">VB.NET</a> IDE of Visual Studio is emitting multiple 'Active Context' priority 600 strings and the Document Explorer is going with Microsoft documents over our ESRI Types. You can see what is being emitted in the 'Active Content' area of the Dynamic Help in Visual Studio by using the Registry Editor (regedit.exe) to find the following registry key: "HEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Dynamic Help" and setting the Data value of the "Display Debug Output in Retail" to "YES". To aid in debugging: I merged a couple of screen shots of the Dynamic Help 'Active Context' emitted strings in Visual Studio with the cursor over the keyword ISceeenDisplay as an attachment (see: F1_Help_issue_VB.NET_1.bmp).<a href="http://VB.NET" target="_blank">VB.NET</a>:Dim screenDisplay As IScreenDisplay = activeView.ScreenDisplayC#:IScreenDisplay screenDisplay = activeView.ScreenDisplay;