Matt Thalman

Results 294 comments of Matt Thalman

Here's the build error when this patch isn't applied: ``` /vmr/.dotnet/sdk/9.0.100-preview.2.24103.2/Sdks/Microsoft.NET.Sdk/targets/Microsoft.PackageDependencyResolution.targets(266,5): error NETSDK1005: Assets file '/vmr/src/roslyn/artifacts/obj/Microsoft.CodeAnalysis.Workspaces.MSBuild.BuildHost/project.assets.json' doesn't have a target for 'net8.0'. Ensure that restore has run and that you...

This is still an issue as explained in https://github.com/dotnet/installer/pull/18752#issuecomment-1961585290. Here's a binlog that demonstrates that net8.0 is being targeted in the VMR by the two projects using the `NetRoslyn` property:...

> > This is still an issue as explained in [dotnet/installer#18752 (comment)](https://github.com/dotnet/installer/pull/18752#issuecomment-1961585290). > > As [I explained](https://github.com/dotnet/roslyn/pull/71704#pullrequestreview-1863834907) the approach in this PR is not the right way to solve the...

Closing in favor of the changes in https://github.com/dotnet/roslyn/pull/72248.

@davidfowl - Does there exist any documentation that might help this request of having guidance for securely configuring ASP.NET Core in container scenarios?

Without Windows ARM, the estimate would be 27 mins for multi-stage and 24 mins for single stage. So the benefit really goes to .NET Fx in that case. Regarding your...

I'd like to revisit this issue because of the increased agent provisioning wait time introduced by the migration to the [Arcade pools](https://github.com/dotnet/docker-tools/pull/954). Wait time for Linux agents averages around 10...

[Triage] - It'd be worthwhile to do a more in-depth analysis on the implementation cost and the scenarios that we care about: 1. Tic-toc scenario: only build the images in...

[Triage] This was first noticed in the https://github.com/dotnet/dotnet-buildtools-prereqs-docker repo where there are some large images that take a long time to run SBOM generation. Some build legs end up pulling...

Effectively it is just adding the FIPS version of OpenSSL to the image and everything else remains the same. .NET can seamlessly work with that OpenSSL library just as it...