UpdateVSConfigurations (#24752)
* Fixed odbc configurations for compat package
* Run UpdateVSConfigurations
* Remove Default Configurations to help VS... comment from csproj's
* Remove from System.Buffers as well
* Replaced ContainsKey() Calls with TryAdd() Dictionary Calls (Where Applicable)
Replaced `ContainsKey()` method calls with the new `TryAdd()` method
where applicable.
* Reverted `TryAdd()` To Previous Approach
Reverted to earlier approach to avoid unnessary allocation of a new
row.
* Cleaned Up `else-if` Usage with `TryAdd()`
Removed the `TryAdd()` call from within the conditional statements and
moved them to the body
* Added Extra Line for Readability / Coding Style
* Updated Non-Dictionary Test Cases To Use `TryAdd()`
Updated various unit tests to include the `TryAdd()` instead of the
previous `ContainsKey()` pattern. This focused primarily on test casts
that were not dictionary-related at all to help curb any potential
regression issues.
* Added `TryAdd()` Within Dictionary Performance Test
Replaced older `ContainsKey()` implementation with newer `TryAdd()`.
* Reverted PerfDictionary Test to `ContainsKey()` Usage
Changed test to earlier implementation in to make way for .NET Core
specific tests using newer API.
* Created Separate .NET Core Dictionary Performance Test
Copied the existing dictionary performance tests (from
`Perf.Dictionary.cs`) and used the newer `TryAdd()` calls; Adjusted the
projects test file only include these when targeting .NET Core.
* Created Separate .NET Core SQL Manual Test
Reverted previous usage of the newer `TryAdd()` method and created a
separate .NET Core specific file to to be conditionally included and
tested.
* Separated .NET Core ILPrinter Test
Reverted previous changes involving the `TryAdd()` method and created a
seperate file to test this functionality only for .NET Core.
* Created Seperate .NET Core Linq TreeManipulation Tests
Reverted previous changes to the normal tests and created a seperate
test targeting .NET Core with the newer `TryAdd()` usage.
* Created Seperate .NET Core xNodeBuilder Test
Reverted previous changes to the normal tests and created a seperate
test targeting .NET Core with the newer `TryAdd()` usage.
* Missed .NET Core Reference for InternalConnectionWrapper
* Applied Compilation Condition for InternalConnectionWrapper to Avoid Collisions
Applied Compilation Condition for InternalConnectionWrapper to Avoid
Collisions (i.e. either build for .NET Core or use the other one for
non-Core builds)
* Avoiding Another Build Collision with .NET Core Functionality
Added a .NET Core compilation constraint for the .NET Core specific
ILPrinter class to avoid issues when building (i.e. only build .NET Core
or non-Core).
* Fixed Yet Another Potential Build Collision with .NET Core
Added a .NET Core compilation constraint for the .NET Core specific
Performance Dictionary testing class to avoid issues when building (i.e.
only build .NET Core or non-Core).
* Removed More Potential .NET Core Compilation Collisions
Added .NET Core specific constraint to seperate Core and non-Core
classes when building
* Additional .NET Core Build Collision Fix
Added an additional condition to separate .NET Core and non-Core builds.
* Added TryAdd Extension Method for Testing
Added an extension method to support `TryAdd()` calls within test cases
across the solution to avoid code duplication.
* Updated Namespace for Dictionary Extension Methods
Changed from `System.Collection.Tests` to `System.Collections.Generic`
as this wasn't actually a test but rather an extension method.
* Removed Previous Duplicate Tests; Added Extension Method
Removed Previous Duplicate Tests; Added Extension Method Usage
* Updated Extension Method Path
Replaced previous relative pathing string with `$(CommonTestPath)`
* Added Missing Generic Type Parameters to TryAdd Extension Method
* Removed Unnecessary Using Statement
* Updated System.Linq.Expressions Tets to use Extension Method
Removed .NET Core duplicate tests; Added reference to new extension
method (from Common\tests)
* Updated System.Private.Xml.Linq .NET Core Tests to Use TryAdd()
Updated System.Private.Xml.Linq .NET Core Tests to Use TryAdd()
extension method.
* Updated System.Collections To Use Dictionary.TryAdd() Extension Method
Removed previous .NET Core duplicated code and references
* Updated Non-ContainsKey() Tests To Use Extension Method
Updated Non-ContainsKey() tests to use the `TryAdd()` extension method
approach
* Extended TryAdd() Extension Method
Updated the existing `TryAdd()` extension method to target any Dictionary
related interfaces (as opposed to Dictionary implementations)
* Updated References in System.Collections.Test
Removed previous .NET Core specific reference; Added extension method
availability
* Added `TryAdd()` Extension Reference
Added the `TryAdd()` extension for some other dictionary tests that rely
on an interface (which now supports the `TryAdd()` method).
* Removed Explicit .NET Core Compilation Constraint
* Fixed Coding Style Issue
Fixed Coding Style Issue of a missing blank line following the closing
gullwing brace for the if-statement.
* Added `<Link>` Section for Extension Method References
Updated all of the previously added extension method `<Compile>`
sections to include a `<Link>` section to improve formatting.
* Added <Link> Section for Dictionary Extensions
Added Missing <Link> Section for Dictionary Extensions
