Search   Articles   Dev Forums   Personalize   Favorites   Member Login   ASP.Net Hosting
DevASP.NET for ASP.NET, VB.NET, XML and C# (C-Sharp) Developers Sunday, November 23, 2008

Dev Articles
Search Directory
ASP.NET
VB.Net
C-Sharp
SQL Server
 
FREE 12 month online training for ASP.NET & MS Expression Studio and a Free copy of MS Expression Web with Windows Server Purchase

Home > Search > .NET Namespaces > EnvDTE > EnvDTE Namespaces
Search:
What's New - What's Hot


How to: Add References to the EnvDTE and EnvDTE80 Namespaces        
Total Hits: 257  |  Today: 0 Author: Microsoft       Rating:  
Read Reviews | Write Review |   Your Rating: 

When you add a reference to EnvDTE or EnvDTE80, you have the choice of using a .NET assembly or a COM library version. The one you should choose depends upon your project. If you are maintaining an older automation application or add-in, you might need to use the COM version of EnvDTE or EnvDTE80. If you are creating a new managed automation application or add-in, though, you will most likely want to use the .NET assembly version....

How to: Access Automation in Console Projects        
Total Hits: 232  |  Today: 0 Author: Microsoft       Rating:  
Read Reviews | Write Review |   Your Rating: 

Automation members are not used exclusively in add-ins, macros, or wizards. You can use them with any Visual Studio project type. The following procedure demonstrates how to reference and use automation objects and members within a console project....

Attaching to Specific Instances of the IDE        
Total Hits: 231  |  Today: 0 Author: Microsoft       Rating:  
Read Reviews | Write Review |   Your Rating: 

There are two ways to attach to a specific instance of the Visual Studio integrated development environment (IDE) when multiple instances are running.Both of these methods use monikers. A moniker is a name that is bound to an object — in this case, the IDE — that can be used to locate, activate, and access the bound object. You do not need specific information about the location of the actual object. In this regard, it works like a shortcut does with a program in Windows....

How to: Get References to the DTE and DTE2 Objects        
Total Hits: 328  |  Today: 0 Author: Microsoft       Rating:  
Read Reviews | Write Review |   Your Rating: 

In the EnvDTE assembly, the DTE object represents the Visual Studio integrated development environment (IDE) and is the highest level object in the automation model hierarchy. All automation applications must have a reference to this object to gain access to the core automation model. That continues to be the case with Visual Studio 2005....

Error Using EnvDTE with VSLangProj Assemblies        
Total Hits: 200  |  Today: 0 Author: Microsoft       Rating:  
Read Reviews | Write Review |   Your Rating: 

If you create a project that references one or more of the VSLangProj assemblies and the EnvDTE assembly, you can occasionally get the following error at runtime:"Unhandled Exception: System.IO.FileNotFoundException: Error while loading file 'EnvDTE,Version=7.0.3300.0"This error is due to a runtime type resolution conflict. That is, the version of EnvDTE that is included with Visual Studio 2005 is 8.0.xx, but the project's configuration reference is looking for an earlier version of this assembl...

EnvDTE Namespace        
Total Hits: 322  |  Today: 0 Author: Microsoft       Rating:  
Read Reviews | Write Review |   Your Rating: 

EnvDTE is an assembly-wrapped COM library containing the objects and members for Visual Studio core automation.Library content is unchanged from prior versions of Visual Studio. All changes and new functionality are contained in EnvDTE80....

EnvDTE Namespace        
Total Hits: 99  |  Today: 0 Author: Microsoft Corporation       Rating:  
Read Reviews | Write Review |   Your Rating: 

EnvDTE is an assembly-wrapped COM library containing the objects and members for Visual Studio core automation. Library content is unchanged from prior versions of Visual Studio. All changes and new functionality are contained in EnvDTE80....



DevASP.Net - Disclaimer - Privacy
Copyright © 2008 DevASP.net