Eric StJohn
Eric StJohn
More info is in this issue in CoreFx https://github.com/dotnet/corefx/issues/17905
I wonder how much of a goal it is to make them all exactly consistent, or just all support an intersection of API? cc @jkotas @stephentoub @ViktorHofer
In that case I'm not sure what this would be tracking since I would expect that to be achieved by creating the contract and committing any baselines.
@akoeplinger can you clarify what you think should happen, or close this if you agree with what's said here?
The behavior is expected. While we try to make .NETFramework library reuse in .NET Core / .NET5+ a possibility, it's not a guarantee. In this case we have conflicting requirements,...
The analyzers are picked up regardless of values for `Exclude` (unfortunately) due to https://github.com/dotnet/sdk/issues/1212. We shouldn't however exclude the targets. I'll update the sample to only exclude compile and runtime.
> generate a package that can be used to let the this project know about the fedora.40-x64 rid. Looks like this is trying to publish crossgen2 as a self-contained application....
We still get a lot of requests for folks not understanding why they get these exceptions in .NETCore. It would be helpful to have documentation covering the limitations of System.Configuration.ConfigurationManger...
cc @dotnet/area-system-configuration
An important thing to cover here -- most configuration sections which were defined by .NETFramework are no longer functional in .NETCore. System.Configuration.ConfigurationManager is only provided for compatibility. Most people who...