- Fix Security Vulnerability in System.Data.SqlClient

- Fix Collation Conflict Risks -- Thanks to Contribution by @simelis

NetStandard.SqlBulkHelpers/CustomExtensions/ReflectionExtensions.cs

@@ -2,8 +2,6 @@
 using System.Collections.Generic;
 using System.Linq;
 using System.Reflection;
-using System.Text;
-using Microsoft.IdentityModel.Protocols;
 using SqlBulkHelpers.CustomExtensions;
 
 namespace SqlBulkHelpers.SqlBulkHelpers.CustomExtensions

NetStandard.SqlBulkHelpers/NetStandard.SqlBulkHelpers.csproj

@@ -8,15 +8,17 @@
 	<PackageLicenseExpression>MIT</PackageLicenseExpression>
     <Authors>BBernard / CajunCoding</Authors>
     <Company>CajunCoding</Company>
-	<Version>2.4.3</Version>
+	<Version>2.4.4</Version>
 	<PackageProjectUrl>https://github.com/cajuncoding/SqlBulkHelpers</PackageProjectUrl>
 	<RepositoryUrl>https://github.com/cajuncoding/SqlBulkHelpers</RepositoryUrl>
     <Description>A library for easy, efficient and high performance bulk insert and update of data, into a Sql Database, from .Net applications. By leveraging the power of the SqlBulkCopy classes with added support for Identity primary key table columns this library provides a greatly simplified interface to process Identity based Entities with Bulk Performance with the wide compatibility of .NetStandard 2.0.</Description>
 	<PackageTags>sql server database table bulk insert update identity column sqlbulkcopy orm dapper linq2sql materialization materialized data view materialized-data materialized-view sync replication replica readonly</PackageTags>
     <PackageReleaseNotes>
-		- Fix Caching bug for Processing Definitions loaded from class Attribute annotations, etc. whereby the FullName was not correctly used resulting in cache conflicts and incorrect values when classes have the same name.
+		- Fix Collation Conflict Risks -- Thanks to Contribution by @simelis
+		- Fix Security Vulnerability in System.Data.SqlClient
 
 		Prior Relese Notes:
+		- Fix Caching bug for Processing Definitions loaded from class Attribute annotations, etc. whereby the FullName was not correctly used resulting in cache conflicts and incorrect values when classes have the same name.
 		- Add Support to manually control if Materialized Loading tables are cleaned-up/removed when using `SchemaCopyMode.OutsideTransactionAvoidSchemaLocks` via `materializeDataContext.DisableMaterializedStagingTableCleanup()`;
 		always enabled by default and throws an `InvalidOperationException` if if SchemaCopyMode.InsideTransactionAllowSchemaLocks is used. This provides support for advanced debugging and control flow support.
 		- Improved SqlBulkHelpers Configuration API to now provide Clone() and Configure() methods to more easily copy/clone existing configuration and change values is specific instances;

README.md

@@ -151,7 +151,6 @@ _Since this functionality is disabled by default it must be enabled via `SqlBulk
 _To minimize the risk of issues dropping/re-creating the FullTextIndex, it is done on a separate connection so that it can be recovered in the case of
 any issues, therefore it requires the use of Concurrent Sql Connections via a `Func<SqlConnection>` connection factory or `ISqlBulkHelpersConnectionProvider` implementation._
 
-
 ## Example Usage for Materializing Data:
 NOTE: Use the [Configuration](#example-configuration-of-defaults) above to improve performance -- particularly when initially loading table schemas for multiple tables (which are cached after initial load).
 
@@ -214,10 +213,17 @@ public class TestDataService
 
 ```
 
-
 ## Nuget Package
 To use in your project, add the [SqlBulkHelpers NuGet package](https://www.nuget.org/packages/SqlBulkHelpers/) to your project.
 
+### v2.4.4 Release Notes:
+- Fix Collation Conflict Risks -- Thanks to Contribution by @simelis [PR](https://github.com/cajuncoding/SqlBulkHelpers/pull/18)
+- Fix Security Vulnerability in System.Data.SqlClient
+
+### v2.4.3 Release Notes:
+- Fix Caching bug for Processing Definitions loaded from class Attribute annotations, etc. whereby the FullName was not correctly used resulting in cache conflicts and 
+incorrect values when classes have the same name.
+
 ### v2.4.2 Release Notes:
 - Add Support to manually control if Materialized Loading tables are cleaned-up/removed when using `SchemaCopyMode.OutsideTransactionAvoidSchemaLocks` via `materializeDataContext.DisableMaterializedStagingTableCleanup()`;
  always enabled by default and throws an `InvalidOperationException` if if SchemaCopyMode.InsideTransactionAllowSchemaLocks is used. This provides support for advanced debugging and control flow support.