Clide 2.5.11

There is a newer version of this package available.
See the version list below for details.
Install-Package Clide -Version 2.5.11
dotnet add package Clide --version 2.5.11
<PackageReference Include="Clide" Version="2.5.11" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Clide --version 2.5.11
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: Clide, 2.5.11"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Clide as a Cake Addin
#addin nuget:?package=Clide&version=2.5.11

// Install Clide as a Cake Tool
#tool nuget:?package=Clide&version=2.5.11
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

High-level, composable and testable APIs for working with IDEs.

NuGet packages (2)

Showing the top 2 NuGet packages that depend on Clide:

Package Downloads




GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
4.1.1 4,048 4/8/2020
4.1.0 209 3/12/2020
4.0.17 984 3/18/2020
4.0.12 185 12/13/2019
3.4.2 1,002 7/12/2019
3.2.68 281 3/18/2019
3.2.60 1,357 2/26/2019
3.1.14 283 12/9/2018
2.5.11 2,017 4/26/2017
1.0.1211.1906 1,868 11/19/2012


* VS services are no longer automatically imported via constructor dependencies.
 This was causing significant performance degradation for little additional
 simplicity over just taking a dependency on a single constructor parameter
 `[Import(typeof(SVsServiceProvider))] IServiceProvider services` which can
 provide the same behavior in a much more explicit way. Typical pattern is
 for this parameter to be used in a public constructor together with the other
 MEF dependencies, and invoke an internal constructor with the actual dependencies
 (i.e. DTE, IVsShell, etc.) which are just extracted from the service provider
 at construction time. Also, this allows the component to decide to delay
 retrieval of these services, marshall to the UI thread as needed, etc.


* Dropped .NET 4.0 and therefore VS2010 support.


* Added general-purpose referencing service


* Added FindProjects extension method for ISolutionNode, which is more efficient than traversing the entire solution.
* Improved support for side-by-side versioning of Clide assemblies deployed by multiple extensions


* Reworked internals to avoid depending on VS-MEF extensibility, which is problematic and may
 cause interference with VS composition.
* Core DI now provided by Autofac, which gives us a performance boost in addition.
* Components now don't need any [Import] or [ImportingConstructor] in order for constructor
 dependencies to work, even for core VS services like IServiceProvider or IVsShell, DTE, etc.
* Types that have the ComponentAttribute applied are automatically registered.
* Supports registering with a certain type (like [Export(typeof(IMyService))]): [Component(typeof(IMyService))]
* Added support for registering components as single instance (singletons) using [Component(IsSingleton = true)]


* Fixes some performance issues due to MEF (lack of) caching
* Tracing of MEF composition off by default (can be turned on for diagnostics via the registry)
* Exposed ServiceLocator.GlobalProvider to get access to a thread-safe IServiceProvider for the entire Visual Studio IDE.
* Removed usage of the problematic ServiceProvider.GlobalProvider (see above)
* Removed usage of the problematic ThreadHelper for UI thread marshaling (now leveraging the WPF Dispatcher)
* Added support for customizing what kinds of traces you want to receive on your output window via Host.Initialize
* Fixed a potential hang when using the Tracer from a background thread
* Fixed issue when a command filter was improperly configured.


* Expose CompositionContainer directly on IDevEnv. This simplifies many scenarios where you want to interact with the container. Users can still import ICompositionService.
* Added support for intercepting arbitrary commands in the IDE via simple exports of ICommandInterceptor components, automatically registered when the host is initialized.
* Moved MEF tracing/diagnostics to run on a separate background thread. This makes host initialization much faster.


* Refactored for easier reuse by offering two static entry points:
    - DevEnv.Get: gets the IDevEnv entry point API. This can be
      used from anywhere you can import an IServiceProvider. By
      default the instance is reused.
    - Host.Initialize: initializes a hosting package and its components
      (i.e. commands, filters, tool windows, etc.).
* Single assembly now can be used for both VS2010 and VS2012: this means
 you no longer have to fork your extension for either IDE just because
 you use Clide (you may because of other dependencies, like VSMSDK).


* ISolutionExplorer API, with full solution traversal, behaviors
 for selecting, expanding and collapsing nodes, etc.
* Integration with Adapter pattern for pluggable conversion of
 solution explorer nodes (i.e. projectNode.As<EnvDTE.Project>())
* Improved diagnostics and debug-time rendering of nodes
* Improved reporting of composition errors in the Clide output window


* Full support for MEF-exported commands (ICommandExtension) and command filters
* ToolWindow support
* Tools options pages support