Clide 2.3.24

.NET Framework 4.0

dotnet add package Clide --version 2.3.24

NuGet\Install-Package Clide -Version 2.3.24

This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.

<PackageReference Include="Clide" Version="2.3.24" />

For projects that support PackageReference, copy this XML node into the project file to reference the package.

paket add Clide --version 2.3.24

The NuGet Team does not provide support for this client. Please contact its maintainers for support.

#r "nuget: Clide, 2.3.24"

#r directive can be used in F# Interactive and Polyglot Notebooks. 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.3.24

// Install Clide as a Cake Tool
#tool nuget:?package=Clide&version=2.3.24

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.
This package provides the core APIs so that your automation can remain IDE-agnostic.
See also Clide.VisualStudio and Clide.XamarinStudio.

Product	Compatible and additional computed target framework versions.
.NET Framework	net40 is compatible. net403 was computed. net45 was computed. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed.

Compatible target framework(s)

Included target framework(s) (in package)

Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

GitHub repositories (1)

Showing the top 1 popular GitHub repositories that depend on Clide:

Repository	Stars
godotengine/godot-csharp-visualstudio Godot C# extension for Visual Studio	257

Version	Downloads	Last updated
2.3.24	121	3/17/2015
2.3.20	192	12/5/2014
2.3.16	101	12/4/2014
2.3.15	112	12/3/2014
2.3.14	100	12/2/2014
2.3.13	105	12/2/2014
2.3.12	112	11/26/2014
2.3.11	146	10/28/2014
2.3.10	125	10/28/2014
2.3.9	95	10/28/2014
2.3.8	96	10/28/2014
2.3.7	107	10/28/2014
2.3.6	136	10/8/2014
2.3.5	137	9/23/2014
2.3.2	170	1/9/2014
2.2.1312.318	104	1/6/2014
2.1.1306.2716	101	6/27/2013
2.1.1306.2619	96	6/26/2013
2.0.1306.1821	97	6/18/2013
2.0.1306.1719	101	6/18/2013
2.0.1306.1119	96	6/11/2013
2.0.1306.1118	98	6/11/2013
2.0.1306.1117	103	6/11/2013
2.0.1306.1015	98	6/10/2013
2.0.1306.816	102	6/8/2013
2.0.1306.719	102	6/7/2013
1.4.1305.2320	104	5/23/2013
1.4.1305.2305	92	5/23/2013
1.4.1305.2302	102	5/23/2013
1.4.1305.2211	92	5/22/2013
1.4.1305.2205	105	5/22/2013
1.4.1305.2120	98	5/21/2013
1.4.1305.1705	105	5/17/2013
1.3.1305.1514	95	5/15/2013
1.3.1301.2116	101	1/21/2013
1.3.1301.1823	95	1/18/2013
1.3.1301.1815	96	1/18/2013
1.3.1301.1721	103	1/18/2013
1.2.1301.1419	104	1/14/2013
1.2.1301.1414	96	1/14/2013
1.2.1301.1016	97	1/10/2013
1.2.1301.921	96	1/9/2013
1.2.1301.915	97	1/9/2013
1.2.1301.903	97	1/9/2013
1.2.1301.821	99	1/8/2013
1.2.1301.820	104	1/8/2013
1.2.1301.816	99	1/8/2013
1.2.1301.420	100	1/4/2013
1.2.1301.323	97	1/3/2013
1.2.1301.320	98	1/3/2013
1.1.1212.1720	92	12/17/2012
1.1.1212.1715	96	12/17/2012
1.1.1212.1405	96	12/14/2012
1.0.1211.3003	95	11/30/2012
1.0.1211.2917	91	11/29/2012
1.0.1211.2813	99	11/28/2012
1.0.1211.2719	101	11/27/2012
1.0.1211.2014	95	11/23/2012
1.0.1211.1917	96	11/19/2012
1.0.1211.1906	91	11/19/2012

v2.2

* Added general-purpose referencing service

v2.1

* 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

v2.0

* 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)]

v1.4

* 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.

v1.3

* 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.

v1.2

* 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).

v1.1

* 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

v1.0

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