DbTestMonkey.Contracts
Metadata
Authors | Justin Cook |
---|---|
Copyrights | Copyright 2015 Justin Cook. All rights reserved. |
Description | Core database library used for assisting with integrations tests that connect to databases. |
Language | en-US |
LicenseUrl | https://github.com/DbTestMonkey/DbTestMonkey/blob/master/License.txt |
Owners | Justin Cook |
ProjectUrl | https://github.com/DbTestMonkey/DbTestMonkey |
ReleaseNotes | v1.0.0 - First stable release. - SQL Server Db Provider and XUnit Test Provider are supported. |
RequireLicenseAcceptance | False |
Tags | unit testing database integration contract managed |
Title | DbTestMonkey.Contracts |
PackageSize | 16765 |
PackageHashAlgorithm | SHA512 |
PackageHash | WruEKdJPLKTDyI/bO+sjX1J04IVeaYZnAppLcTiflZ73FdZX92vru827qZ/Ou/8KChaOn62u2v2QSX2R74rqmA== |
DownloadCount | 000000 |
CreatedDate | 2015-09-09T05:24:31 |
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 DbTestMonkey.Contracts -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install DbTestMonkey.Contracts -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 DbTestMonkey.Contracts
- Installing the package (HTTP Basic authentication):
-
Install-Package DbTestMonkey.Contracts -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package DbTestMonkey.Contracts -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package DbTestMonkey.Contracts
OpenWrap
- Installing the package:
-
o add-wrap DbTestMonkey.Contracts
- Uninstalling the package:
-
o remove-wrap DbTestMonkey.Contracts
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.