FubarDev.Lexware.Database.Faktura
Metadata
| Authors | Fubar Development Junker |
|---|---|
| Copyrights | Copyright 2015 Fubar Development Junker |
| Description | Lexware-Entitäten für Faktura |
| LicenseUrl | http://opensource.org/licenses/MIT |
| Owners | Fubar Development Junker |
| ProjectUrl | https://github.com/FubarDevelopment/Lexware |
| ReleaseNotes | Erstes Release |
| RequireLicenseAcceptance | False |
| Tags | Lexware DB Datenbank Database Access Zugriff Faktura |
| Dependencies | NodaTime:1.3.1|FubarDev.Lexware.Database.Shared:0.1.0 |
| PackageSize | 35887 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | aCH4zM78szKJVXiwfg1yIs1Uz2EgMMULJwZu9a/iERTYTOmsmdY04GlkgHEISrss3Kn0F6d4m3x3AE3Opo0+tA== |
| DownloadCount | 000000 |
| CreatedDate | 2015-10-08T11:42:13 |
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 FubarDev.Lexware.Database.Faktura -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install FubarDev.Lexware.Database.Faktura -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 FubarDev.Lexware.Database.Faktura
- Installing the package (HTTP Basic authentication):
-
Install-Package FubarDev.Lexware.Database.Faktura -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package FubarDev.Lexware.Database.Faktura -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package FubarDev.Lexware.Database.Faktura
OpenWrap
- Installing the package:
-
o add-wrap FubarDev.Lexware.Database.Faktura
- Uninstalling the package:
-
o remove-wrap FubarDev.Lexware.Database.Faktura
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.