1.0.1 - update target frameworks and readme

agertenbach · Dec 11, 2023 · 59d8668 · 59d8668
1 parent 4be14b4
commit 59d8668
Show file tree

Hide file tree

Showing 5 changed files with 34 additions and 7 deletions.
diff --git a/LogDeferred.WebApplicationBuilder/LogDeferred.WebApplicationBuilder.csproj b/LogDeferred.WebApplicationBuilder/LogDeferred.WebApplicationBuilder.csproj
@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
 	<PropertyGroup>
-		<Version>1.0.0</Version>
+		<Version>1.0.1</Version>
 		<Authors>Adam Gertenbach</Authors>
 		<Product>LogDeferred.WebApplicationBuilder</Product>
 		<Description>Enables deferred logging against the WebApplicationBuilder during services registration using familiar ILogger abstractions plus dependency injection</Description>

diff --git a/LogDeferred.WebApplicationBuilder/readme.md b/LogDeferred.WebApplicationBuilder/readme.md
@@ -101,7 +101,7 @@ With the deferred logging available from the start, I can get a better picture o
           Feature One is enabled
     info: MyApplication.Services.DatabaseProvider[0]
           Database provider is Local
-    info: MyApplication.Services.FeatureOne[0]
+    warn: MyApplication.Services.FeatureOne[0]
           Feature one doesn't have a valid connection string!
     info: MyApplication.Services.DatabaseProvider[0]
           Here is other useful DatabaseProvider information
@@ -160,6 +160,8 @@ For example:
 
 will result in the log `Mode is 2` because both calls to `Configure` occur before the host starts and the value is computed.
 
+If the host fails to start, deferred logs will not be produced. If you must ensure that logs are recorded regarding the starting of the host, you should still consider bootstrapping a logger for immediate access.
+
 ### Customizing the default startup logger name
 Since the extensions are running against the `IServiceCollection` directly, we must specify a default logger category for any log events if a type parameter is not supplied. To keep the naming approximately consistent with other logging occurring as the host starts, we opted for "Microsoft.Hosting.Startup". 
 

diff --git a/LogDeferred/LogDeferred.csproj b/LogDeferred/LogDeferred.csproj
@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
 	<PropertyGroup>
-		<Version>1.0.0</Version>
+		<Version>1.0.1</Version>
 		<Authors>Adam Gertenbach</Authors>
 		<Product>LogDeferred</Product>
 		<Description>Enables deferred logging against the IServiceCollection during services registration using familiar ILogger abstractions plus dependency injection</Description>
@@ -11,7 +11,7 @@
 		<RootNamespace>LogDeferred</RootNamespace>
 		<GeneratePackageOnBuild>true</GeneratePackageOnBuild>
 		<GenerateDocumentationFile>true</GenerateDocumentationFile>
-		<TargetFrameworks>netstandard2.1</TargetFrameworks>
+		<TargetFrameworks>netstandard2.1;net6.0;net7.0;net8.0</TargetFrameworks>
 		<RepositoryUrl>https://github.com/agertenbach/LogDeferred</RepositoryUrl>
 		<PackageProjectUrl>https://github.com/agertenbach/LogDeferred</PackageProjectUrl>
 		<PackageTags>ILogger Startup Logging Registration IServiceCollection</PackageTags>
@@ -20,13 +20,34 @@
 		<Nullable>enable</Nullable>
 	</PropertyGroup>
 
-	<ItemGroup>
+	<ItemGroup Condition="$(TargetFramework) == 'netstandard2.1'">
 		<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="3.0.0" />
 		<PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="3.0.0" />
 		<PackageReference Include="Microsoft.Extensions.Options" Version="3.0.0" />
 		<PackageReference Include="Microsoft.Extensions.Hosting" Version="3.0.0" />
 	</ItemGroup>
 
+	<ItemGroup Condition="$(TargetFramework) == 'net6.0'">
+		<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="6.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="6.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Options" Version="6.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Hosting" Version="6.0.0" />
+	</ItemGroup>
+
+	<ItemGroup Condition="$(TargetFramework) == 'net7.0'">
+		<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="7.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="7.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Options" Version="7.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Hosting" Version="7.0.0" />
+	</ItemGroup>
+
+	<ItemGroup Condition="$(TargetFramework) == 'net8.0'">
+		<PackageReference Include="Microsoft.Extensions.DependencyInjection.Abstractions" Version="8.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Logging.Abstractions" Version="8.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Options" Version="8.0.0" />
+		<PackageReference Include="Microsoft.Extensions.Hosting" Version="8.0.0" />
+	</ItemGroup>
+
 	<ItemGroup>
 		<None Include="readme.md" Pack="true" PackagePath="\"/>
 		<None Include="license.md" Pack="true" PackagePath="\"/>

diff --git a/LogDeferred/readme.md b/LogDeferred/readme.md
@@ -101,7 +101,7 @@ With the deferred logging available from the start, I can get a better picture o
           Feature One is enabled
     info: MyApplication.Services.DatabaseProvider[0]
           Database provider is Local
-    info: MyApplication.Services.FeatureOne[0]
+    warn: MyApplication.Services.FeatureOne[0]
           Feature one doesn't have a valid connection string!
     info: MyApplication.Services.DatabaseProvider[0]
           Here is other useful DatabaseProvider information
@@ -160,6 +160,8 @@ For example:
 
 will result in the log `Mode is 2` because both calls to `Configure` occur before the host starts and the value is computed.
 
+If the host fails to start, deferred logs will not be produced. If you must ensure that logs are recorded regarding the starting of the host, you should still consider bootstrapping a logger for immediate access.
+
 ### Customizing the default startup logger name
 Since the extensions are running against the `IServiceCollection` directly, we must specify a default logger category for any log events if a type parameter is not supplied. To keep the naming approximately consistent with other logging occurring as the host starts, we opted for "Microsoft.Hosting.Startup". 
 

diff --git a/readme.md b/readme.md
@@ -101,7 +101,7 @@ With the deferred logging available from the start, I can get a better picture o
           Feature One is enabled
     info: MyApplication.Services.DatabaseProvider[0]
           Database provider is Local
-    info: MyApplication.Services.FeatureOne[0]
+    warn: MyApplication.Services.FeatureOne[0]
           Feature one doesn't have a valid connection string!
     info: MyApplication.Services.DatabaseProvider[0]
           Here is other useful DatabaseProvider information
@@ -160,6 +160,8 @@ For example:
 
 will result in the log `Mode is 2` because both calls to `Configure` occur before the host starts and the value is computed.
 
+If the host fails to start, deferred logs will not be produced. If you must ensure that logs are recorded regarding the starting of the host, you should still consider bootstrapping a logger for immediate access.
+
 ### Customizing the default startup logger name
 Since the extensions are running against the `IServiceCollection` directly, we must specify a default logger category for any log events if a type parameter is not supplied. To keep the naming approximately consistent with other logging occurring as the host starts, we opted for "Microsoft.Hosting.Startup".