After installing VS.NET 2003, "DTE.OLB COULD NOT BE Load.please Re-Run Setup and Repair Your Installation" cannot star

xiaoxiao2021-03-06  106

After installing VS.NET 2003, "DTE.OLB COULD NOT BE Load.Please Re-Run Setup and Repair Your Installation" cannot be launched (WellkNow Posted 2004-8-24 17:19:13)

By searching, it is found that DTEV.OLB is in X: / Program Files / Common files / Microsoft Shared / Msenv to use the regsvr32 manual registration, IDE can start normally. Checked MSDN, there is a corresponding article description ========================================= ============================================= PRB: Visual IDE Does not open when it Started or Application Cannot Start Error Message http://support.microsoft.com/default.aspx?scid=kb;n-us;306905 So what is this file? View MSDN content as follows: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsdebugext/html/vxlrfenvdtedebugger.asp It contains Envdte namespace, the Assembly name is Envdte. All objects, members and automation models of Visual Studio .NET are based on DTE objects. DTE objects represent Visual Studio .NET IDE, which is located in the top level of the automated model class. Contains in envdte.dll. The COM type library name is "Microsoft Development Environment 7.0" is included in DTE.OLB. Simply sentence, it represents IDE, we can use it to extend vs.net IDE because all automation objects require DTE objects, so if No registration is registered, IDE certainly does not work properly. By the way, I don't have my own references. Select .NET Assembly or COM relies on engineering type. (If you use the add_ins wizard or macro, then you don't need to add a reference manually, but if you are using it outside, you must manually add a reference) reference method is from "Solution Explorer" in "Add reference" "Add Envdte" or "Microsoft Development Environment 7.0" (above the method of VB and C #).

) An example of a specific use: Programmatically Adding a UserControl to the VS.NET ToolBox Author: Shawn A. Van Ness example demonstrates VS.NET add to the Microsoft Tablet PC SDK's InkPicture and InkEdit Toolbox private static void AddToolBoxTab (EnvDTE.DTE env) {// First, ensure Tablet SDK is installed - get location of Microsoft.Ink.dll string fullpathToMicrosoftInk = LookupMicrosoftInkAssemblyFilename (); // Prepare to munge the toolbox - get toolbox window, object, and tabs collection EnvDTE.Window toolboxWindow = env.Windows.Item (EnvDTE.Constants.vsWindowKindToolbox); EnvDTE.ToolBox toolbox = (EnvDTE.ToolBox) toolboxWindow.Object; EnvDTE.ToolBoxTabs toolboxTabs = toolbox.ToolBoxTabs; // Careful to check if our tab already exists foreach ( Envdte.toolboxtab Tab in Toolboxtabs) {if (Tab.Name == TabName) Return;} // no, so add it envdte.toolboxtab newTab = Toolboxtabs.add (tabname); // wi nBug: gotta show the Properties window, first (this cost me ~ 1 day of my life) env.ExecuteCommand ( "View.PropertiesWindow", ""); // WinBug2: gotta activate the tab and select the first item (grr. ..) newtab.Activate (); newtab.ToolBoxItems.Item (1) .Select (); // Finally: add the Microsoft Ink controls newtab.ToolBoxItems.Add (@ "? Unused", fullpathToMicrosoftInk, EnvDTE.vsToolBoxItemFormat.vsToolBoxItemFormatDotNETComponent } Private static string lookupmicrosoftinkassemblyFileName () {microsoft.win32.registryKey rk = microsoft.win32.registry.localmachine;

转载请注明原文地址:https://www.9cbs.com/read-122960.html

New Post(0)