-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #50 from akkadotnet/dev
v1.3.6 Release
- Loading branch information
Showing
30 changed files
with
984 additions
and
213 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
|
|
||
| Microsoft Visual Studio Solution File, Format Version 12.00 | ||
| # Visual Studio 15 | ||
| VisualStudioVersion = 15.0.27130.2027 | ||
| MinimumVisualStudioVersion = 10.0.40219.1 | ||
| Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Akka.Logger.Serilog", "src\Akka.Logger.Serilog\Akka.Logger.Serilog.csproj", "{E945AABA-2779-41E8-9B43-8898FFD64F22}" | ||
| EndProject | ||
| Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Akka.Logger.Serilog.Tests", "src\Akka.Logger.Serilog.Tests\Akka.Logger.Serilog.Tests.csproj", "{0F9B9BC6-9F86-40E8-BA9B-D27BF3AC7970}" | ||
| EndProject | ||
| Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Akka.Logger.Serilog.Tests.Performance", "src\Akka.Logger.Serilog.Tests.Performance\Akka.Logger.Serilog.Tests.Performance.csproj", "{CAE7CA7C-0D0C-4FDA-BDE9-BE16A27343EF}" | ||
| EndProject | ||
| Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "build", "build", "{489D8D37-C3F7-477D-9AC7-12DA1621B2CE}" | ||
| ProjectSection(SolutionItems) = preProject | ||
| build.cmd = build.cmd | ||
| build.fsx = build.fsx | ||
| build.ps1 = build.ps1 | ||
| build.sh = build.sh | ||
| EndProjectSection | ||
| EndProject | ||
| Global | ||
| GlobalSection(SolutionConfigurationPlatforms) = preSolution | ||
| Debug|Any CPU = Debug|Any CPU | ||
| Release|Any CPU = Release|Any CPU | ||
| EndGlobalSection | ||
| GlobalSection(ProjectConfigurationPlatforms) = postSolution | ||
| {E945AABA-2779-41E8-9B43-8898FFD64F22}.Debug|Any CPU.ActiveCfg = Debug|Any CPU | ||
| {E945AABA-2779-41E8-9B43-8898FFD64F22}.Debug|Any CPU.Build.0 = Debug|Any CPU | ||
| {E945AABA-2779-41E8-9B43-8898FFD64F22}.Release|Any CPU.ActiveCfg = Release|Any CPU | ||
| {E945AABA-2779-41E8-9B43-8898FFD64F22}.Release|Any CPU.Build.0 = Release|Any CPU | ||
| {0F9B9BC6-9F86-40E8-BA9B-D27BF3AC7970}.Debug|Any CPU.ActiveCfg = Debug|Any CPU | ||
| {0F9B9BC6-9F86-40E8-BA9B-D27BF3AC7970}.Debug|Any CPU.Build.0 = Debug|Any CPU | ||
| {0F9B9BC6-9F86-40E8-BA9B-D27BF3AC7970}.Release|Any CPU.ActiveCfg = Release|Any CPU | ||
| {0F9B9BC6-9F86-40E8-BA9B-D27BF3AC7970}.Release|Any CPU.Build.0 = Release|Any CPU | ||
| {CAE7CA7C-0D0C-4FDA-BDE9-BE16A27343EF}.Debug|Any CPU.ActiveCfg = Debug|Any CPU | ||
| {CAE7CA7C-0D0C-4FDA-BDE9-BE16A27343EF}.Debug|Any CPU.Build.0 = Debug|Any CPU | ||
| {CAE7CA7C-0D0C-4FDA-BDE9-BE16A27343EF}.Release|Any CPU.ActiveCfg = Release|Any CPU | ||
| {CAE7CA7C-0D0C-4FDA-BDE9-BE16A27343EF}.Release|Any CPU.Build.0 = Release|Any CPU | ||
| EndGlobalSection | ||
| GlobalSection(SolutionProperties) = preSolution | ||
| HideSolutionNode = FALSE | ||
| EndGlobalSection | ||
| GlobalSection(ExtensibilityGlobals) = postSolution | ||
| SolutionGuid = {6F6A6366-6F90-4FC6-8E46-861B3CB6C12B} | ||
| EndGlobalSection | ||
| EndGlobal |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,64 @@ | ||
| #### Akka.Logger.Serilog #### | ||
|
|
||
| This is the Serilog integration plugin for Akka.NET. Please check out our [documentation](http://getakka.net/articles/utilities/serilog.html) on how to get the most out of this plugin. | ||
|
|
||
| Targets Serilog 2.6.0 | ||
|
|
||
| # Akka.Logger.Serilog | ||
|
|
||
| This is the Serilog integration plugin for Akka.NET. Please check out our [documentation](http://getakka.net/articles/utilities/serilog.html) on how to get the most out of this plugin. | ||
|
|
||
| Targets Serilog 2.6.0. | ||
|
|
||
| ### Semantic Logging Syntax | ||
| If you intend on using any of the Serilog semantic logging formats in your logging strings, __you need to use the SerilogLoggingAdapter__ inside your instrumented code or there could be elsewhere inside parts of your `ActorSystem`: | ||
|
|
||
| ```csharp | ||
| var log = Context.GetLogger<SerilogLoggingAdapter>(); // correct | ||
| log.Info("My boss makes me use {semantic} logging", "semantic"); // serilog semantic logging format | ||
| ``` | ||
|
|
||
| This will allow all logging events to be consumed anywhere inside the `ActorSystem`, including places like the Akka.NET TestKit, without throwing `FormatException`s when they encounter semantic logging syntax outside of the `SerilogLogger`. | ||
|
|
||
| ## 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: | ||
|
|
||
| ``` | ||
| <Import Project="..\common.props" /> | ||
| ``` |
Oops, something went wrong.