* Create markdownlint.yml

* Create markdownlint-problem-matcher.json

* Create .markdownlint.json

* Update .markdownlint.json

* fix violations

* fixes

* Remove "push" section

As advised by @viktorhofer so it's quite clear it only runs in CI.
Co-authored-by: NDan Moseley <danmose@microsoft.com>

This only affects target sites which are not cross-compiled for a TFM where the static HashData methods don't exist.

Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: NMarek Safar <marek.safar@gmail.com>

Http2Connection.ChangeInitialWindowSize locks connection's SyncObject and calls Http2Stream.OnWindowUpdate which locks stream's SyncObject.
Http2Stream.Complete is called only while stream's SyncObject lock is take and then it calls Http2Connection.RemoveStream that locks connection SyncObject.

Contributes to https://github.com/dotnet/runtime/issues/43865.

* mark FileStream.Lock and Unlock as unsupported on macOS

* update ref assembly

* annotate types derived from FileStream

* annotate VisualBasic parts as well

* Consolidate ComWrappers implementation across platforms
This should help in implementing https://github.com/dotnet/runtimelab/issues/306

* Fix incorrect and missing partial declarations

* Update src/libraries/System.Private.CoreLib/src/System/Runtime/InteropServices/ComWrappers.cs
Co-authored-by: NJan Kotas <jkotas@microsoft.com>

* Adding non ectensions library to transport package and moving transport package to all config leg

* update servicing policy doc

* change name from Microsoft.Extensions.Internal.Transport -> Microsoft.AspNetCore.Internal.Transport

* make isAspnetCore property explicit

* csproj to proj change

* remove non used extensions assemblies from transport package

* Update Directory.Build.props

* InternalGetAssemblyName can open the image !refonly

Initially this was opening in refonly mode in order to be able to get
the name of problematic assemblies.  See
d64b25aa

However that concept doesn't exist anymore in netcore mono.  So open
the image normally.

* Get rid of MonoImage ref_only field

* no refonly mono_domain_get_assemblies

* no refonly arg to assembly search hooks

* No refonly preload hook

* No refonly assembly_loaded_internal

* No refonly mono_error_set_simple_file_not_found

* There's no GAC or shadow copying

* Remove MonoAssembly in_gac field

* remove unused var

* remove MONO_ASMCTX_REFONLY

* Also remove mono_image_open_from_data_internal refonly arg

* Remove console-null console-win32 dead icalls

* Remove shadow copying remains

No more MonoDomain shadow_serial field

* No MonoDomain socket assembly fields

* remove MonoRuntimeInfo arg from mono_assembly_load_corlib

* delete useless allocations

* Update dependencies from https://github.com/dotnet/arcade build 20210205.5

Microsoft.DotNet.XUnitExtensions , Microsoft.DotNet.VersionTools.Tasks , Microsoft.DotNet.Build.Tasks.TargetFramework.Sdk , Microsoft.DotNet.Build.Tasks.Packaging , Microsoft.DotNet.Build.Tasks.Installers , Microsoft.DotNet.Build.Tasks.Feed , Microsoft.DotNet.Build.Tasks.Archives , Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.ApiCompat , Microsoft.DotNet.CodeAnalysis , Microsoft.DotNet.XUnitConsoleRunner , Microsoft.DotNet.GenFacades , Microsoft.DotNet.GenAPI , Microsoft.DotNet.RemoteExecutor , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SharedFramework.Sdk
 From Version 6.0.0-beta.21101.7 -> To Version 6.0.0-beta.21105.5

* Fix xunit analyzer warning in SharedArrayBufferTests.cs
Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: NStephen Toub <stoub@microsoft.com>

* Cleanup the assembly loading code.

* Remove the 'problematic' assembly code.
Co-authored-by: NAleksey Kliger (λgeek) <alklig@microsoft.com>

* Remove the remainder of the appdomain unload code.

* Restore public API functions.

* Add crossgen2 automated SuperPMI collection of Core_Root libraries

Linux is excluded; there are uninvestigated crashes doing crossgen2 Linux collections.

I added logic to copy the runtime ".dotnet" directory to Helix machines to use as the
driver for crossgen2, but that doesn't work for cross-platform scenarios (e.g., Windows
x64 .dotnet, x86 Core_Root), so it's commented out for now and the same-Core_Root corerun.exe
is used as the crossgen2 driver.

Add `-collection_type` argument to superpmi-setup.py

Allow copying of .json files to Helix; needed by crossgen2.

Changed superpmi pipeline to run with DEBUG level logging from superpmi.py so it's
easier to see what happened when looking at Helix logs (without having to find and separately
download the superpmi.log file).

Changed superpmi.py to write stdout/stderr files to log on failure, so we can see why
crossgen2 failed.

Fix creation of log file directories when `-log_file` argument specified

Excluded many more native files from superpmi collection setup.

Fixes #47541

Extra:
1. If `-temp_dir` is specified to superpmi.py, normalize it to
an absolute path.
2. Add a superpmi.py collect `-exclude` option to avoid collecting
assemblies known to fail (and cause pop-up failures: see #47552).
(This isn't used by the automated collection, but is generally useful.)
3. Stop logging too-verbose message about CORINFO_SIG_INST handle
array illegal values, since it's "by design" for crossgen2
4. Force lower-casing of JIT-EE version string, for consistency.

Remove unused fields/functions.

* Remove unused fields from ref.emit classes.

* Remove MonoDynamicImage->run/save, they are always TRUE/FALSE.

* Remove more code.

- Enables MemoryExtensions.AsSpan(T[], Range) to be trimmed in a default Blazor wasm app.
- Use of span.Slice(int) is more efficient than span[int..]
- Use of AsSpan(int, int) is more efficient than AsSpan(Range)

We'd removed this almost a year ago, but it came back almost immediately and accidentally as a result of two PRs that raced with each other.

- Use TryEnsureSufficientExecutionStack rather than EnsureSufficientExecutionStack, allowing the latter to be trimmed in a default Blazor wasm app.
- Use ValueTuple instead of Tuple, allowing the latter to be trimmed in a default Blazor wasm app
- Clean up awaiter usage in RunOnEmptyStackCore

The former just checks the input, and if it's null, calls the latter.

All of our call sites to it pass in a const StringComparison; GetHashCode will then turn around and decide which property on StringComparer to use, and then call GetHashCode on the relevant instance... we may as well just pick the instance directly, which not only saves the lookup and enables devirtualization, it also enables better trimming, as string.GetHashCode(StringComparison) ends up rooting all of the StringComparer properties in case you pass in the appropriate StringComparison.

For a rare path, GetCanonicalPath is removing one character from a string and then inserting  a replacement character.  Thanks to span, we can replace the two string allocations with a single char[] allocation and avoid these Remove/Insert calls, which are the only ones keeping string.Remove and string.Insert from being trimmed out of a default Blazor wasm app.

Fixes NameHeaderValue validation to be in line with RFC.

Resolves #1504

* [reflection] Remove sre-save and DISABLE_REFLECTION_EMIT_SAVE

* remove old sre-save entrypoint declarations too

* mono: remove ENABLE_NETCORE and associated framework code

* Remove g_assert_not_netcore

* No more locales.h

* No more filewatcher.h

* Fix Windows build

* Remove g_assert_netcore

I don't see anything calling this

* Add now-needed include

* Set diagnostic severity

* Fix violations in System.Private.Xml

* Revert .editorconfig

* Remove a couple LINQ usages in Microsoft.Extensions

* Respond to PR feedback.

Change ParameterDefaultValue to use GetUninitializedObject instead of Activator.CreateInstance (#47722)

* Change ParameterDefaultValue to use GetUninitializedObject instead of Activator.CreateInstance

Activator.CreateInstance has the ability to call a parameterless constructor (if one is defined) on a value type. This is incorrect for ParameterDefaultValue. It is more correct to call GetUninitializedObject, which is the same as using `default(T)`.

* Add test for struct with default constructor