NCode.ReparsePoints
Metadata
| Authors | NCode Group |
|---|---|
| Copyrights | Copyright © 2015 NCode Group |
| Description | This library provides an API to create and inspect win32 file and folder reparse points such as hard links, junctions (aka soft links), and symbolic links. |
| LicenseUrl | https://raw.githubusercontent.com/NCodeGroup/NCode.ReparsePoints/master/LICENSE.txt |
| Owners | NCode Group |
| ProjectUrl | https://github.com/NCodeGroup/NCode.ReparsePoints |
| ReleaseNotes | Built on 2015-07-27T04:00-0500. |
| RequireLicenseAcceptance | False |
| Tags | hardlink softlink junction symboliclink win32 link |
| Title | NCode.ReparsePoints |
| PackageSize | 45217 |
| PackageHashAlgorithm | SHA512 |
| PackageHash | bVhzHwcw3mObL/aJj1iaze6TJlms37hYCW0iBeUXNwuL4SEgQdtFSBg8U+B8DmafMGc/20cpM6bzBi8ol3xZKg== |
| DownloadCount | 000000 |
| CreatedDate | 2015-07-27T09:01:37 |
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 NCode.ReparsePoints -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
nuget install NCode.ReparsePoints -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 NCode.ReparsePoints
- Installing the package (HTTP Basic authentication):
-
Install-Package NCode.ReparsePoints -Source http://nuget.gw.symbolsource.org/Public/NuGet/FeedService.mvc
- Installing the package (pre-authenticated):
-
Install-Package NCode.ReparsePoints -Source http://nuget.gw.symbolsource.org/Public/%login%/%key%/NuGet/FeedService.mvc
- Uinstalling the package:
-
Uninstall-Package NCode.ReparsePoints
OpenWrap
- Installing the package:
-
o add-wrap NCode.ReparsePoints
- Uninstalling the package:
-
o remove-wrap NCode.ReparsePoints
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.