Ninject.Extensions.bbvEventBroker
Metadata
| Authors | Ninject Project Contributors |
|---|---|
| Description | Ninject extension which adds support for bbv.Common.EventBroker |
| Language | en-US |
| LicenseUrl | https://github.com/ninject/ninject.extensions.bbveventbroker/raw/master/LICENSE.txt |
| Owners | Ninject Project Contributors |
| RequireLicenseAcceptance | True |
| Dependencies | Ninject:3.0.0-unstable|Ninject.Extensions.ContextPreservation:3.0.0-unstable|Ninject.Extensions.NamedScope:3.0.0-unstable|bbv.Common.EventBroker:[7.1, 7.2) |
| PackageSize | 36342 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | CoLif90MTznQAb7dTWMGQxCjoERX2bRdjHCfTuCFwLJLThuRbMFNljM09PFqpzYFeCWZw1RblVb8IRGiCtzpgQ== |
| DownloadCount | 000000 |
| CreatedDate | 2014-03-20T13:40:25 |
Access
You can access data for this project using the tools and addresses described below.
NuGet (nuget.exe)
- Installing the package (HTTP Basic authentication):
-
nuget install Ninject.Extensions.bbvEventBroker -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install Ninject.Extensions.bbvEventBroker -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
NuGet (Package Manager Console)
- Installing the package (search all configured feeds):
-
Install-Package Ninject.Extensions.bbvEventBroker
- Installing the package (HTTP Basic authentication):
-
Install-Package Ninject.Extensions.bbvEventBroker -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package Ninject.Extensions.bbvEventBroker -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package Ninject.Extensions.bbvEventBroker
OpenWrap
- Installing the package:
-
o add-wrap Ninject.Extensions.bbvEventBroker
- Uninstalling the package:
-
o remove-wrap Ninject.Extensions.bbvEventBroker
Versions
A version is snapshot of a project's source code. It does not need to follow the Major.Minor.Revision.Build numbering pattern. It can be an arbitrary string of text that identifies a release or a build, in particular including meaningful words like beta, RC or RTM.