Viktor Hofer

As this issue is quite old, what's the current stance on this? I believe given the time that netstandard2.0 has been around and successful, is now the right time to...

> Other than slightly more complex code (#ifdefs) and a larger NuGet package download size, I don't think it's "hurting" anyone to keep netstandard1.3 support. Is there any particular urgency...

> I think I see a trend here... any particular reason why this is an important issue for MySqlConnector? From the other thread. When .NET Standard 2.0 was added to...

> (Or are you only describing what happens if it's installed into a project that itself targets netstandard1.3?) Right, the latter. You only get the transitive dependencies that are applicable...

Replied offline: > You will need to add the compatibility difference to the suppression file that is used when comparing net7.0 against net6.0: [runtime/ApiCompatBaseline.NetCoreAppLatestStable.xml at main · dotnet/runtime (github.com)](https://github.com/dotnet/runtime/blob/main/src/libraries/apicompat/ApiCompatBaseline.NetCoreAppLatestStable.xml). You...

cc @smasher164

cc @ahsonkhan @steveharter

@jeffschwMSFT this infrastructure change is necessary to successfully build 7.0.x servicing bits. This [was already part of release/6.0](https://github.com/dotnet/runtime/blob/cdf48abd370f148a537960141f73769e678660e7/src/coreclr/.nuget/Directory.Build.props#L21-L23) but was never forward ported into main. Please see the linked issue...

I don't think so. Seems to be another AzDO flakiness/outage: ``` ##[warning]Git fetch failed with exit code 128, back off 7.517 seconds before retry. git --config-env=http.extraheader=env_var_http.extraheader fetch --force --tags --prune...

@jkotas who would be the right person to review the ILCompiler and Crossgen2 changes?