文件列表:

LICENSE (11341, 2018-10-27)
RELEASE_NOTES.md (44, 2018-10-27)
Versionator.sln (2430, 2018-10-27)
build.cmd (36, 2018-10-27)
build.fsx (9074, 2018-10-27)
build.ps1 (6059, 2018-10-27)
build.sh (3398, 2018-10-27)
docs (0, 2018-10-27)
docs\api (0, 2018-10-27)
docs\api\index.md (10, 2018-10-27)
docs\articles (0, 2018-10-27)
docs\articles\index.md (39, 2018-10-27)
docs\articles\toc.yml (37, 2018-10-27)
docs\docfx.json (1316, 2018-10-27)
docs\images (0, 2018-10-27)
docs\images\icon.png (841, 2018-10-27)
docs\index.md (28, 2018-10-27)
docs\toc.yml (104, 2018-10-27)
docs\web.config (224, 2018-10-27)
serve-docs.cmd (75, 2018-10-27)
serve-docs.ps1 (714, 2018-10-27)
src (0, 2018-10-27)
src\Versionator.Tests.Performance (0, 2018-10-27)
src\Versionator.Tests.Performance\UnitTest1.cs (730, 2018-10-27)
src\Versionator.Tests.Performance\Versionator.Tests.Performance.csproj (559, 2018-10-27)
src\Versionator.Tests (0, 2018-10-27)
src\Versionator.Tests\UnitTest1.cs (168, 2018-10-27)
src\Versionator.Tests\Versionator.Tests.csproj (632, 2018-10-27)
src\Versionator (0, 2018-10-27)
src\Versionator\Class1.cs (80, 2018-10-27)
src\Versionator\Versionator.csproj (231, 2018-10-27)
src\common.props (576, 2018-10-27)

# Versionator Update this readme file with your details. ## Building this solution To run the build script associated with this solution, execute the following: **Windows** ``` c:\> build.cmd all ``` **Linux / OS X** ``` c:\> build.sh all ``` If you need any information on the supported commands, please execute the `build.[cmd|sh] help` command. This build script is powered by [FAKE](https://fake.build/); please see their API documentation should you need to make any changes to the [`build.fsx`](build.fsx) file. ### Conventions The attached build script will automatically do the following based on the conventions of the project names added to this project: * Any project name ending with `.Tests` will automatically be treated as a [XUnit2](https://xunit.github.io/) project and will be included during the test stages of this build script; * Any project name ending with `.Tests` will automatically be treated as a [NBench](https://github.com/petabridge/NBench) project and will be included during the test stages of this build script; and * Any project meeting neither of these conventions will be treated as a NuGet packaging target and its `.nupkg` file will automatically be placed in the `bin\nuget` folder upon running the `build.[cmd|sh] all` command. ### DocFx for Documentation This solution also supports [DocFx](http://dotnet.github.io/docfx/) for generating both API documentation and articles to describe the behavior, output, and usages of your project. All of the relevant articles you wish to write should be added to the `/docs/articles/` folder and any API documentation you might need will also appear there. All of the documentation will be statically generated and the output will be placed in the `/docs/_site/` folder. #### Previewing Documentation To preview the documentation for this project, execute the following command at the root of this folder: ``` C:\> serve-docs.cmd ``` This will use the built-in `docfx.console` binary that is installed as part of the NuGet restore process from executing any of the usual `build.cmd` or `build.sh` steps to preview the fully-rendered documentation. For best results, do this immediately after calling `build.cmd buildRelease`. ### Release Notes, Version Numbers, Etc This project will automatically populate its release notes in all of its modules via the entries written inside [`RELEASE_NOTES.md`](RELEASE_NOTES.md) and will automatically update the versions of all assemblies and NuGet packages via the metadata included inside [`common.props`](src/common.props). If you add any new projects to the solution created with this template, be sure to add the following line to each one of them in order to ensure that you can take advantage of `common.props` for standardization purposes: ``` ```

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：