Now that razor is on .NET 9 arcade, it can switch over to the new control schema. For this repo, this is roughly:
- DotNetBuildFromSource -> DotNetBuildSourceOnly - Building a source-only build.
- DotnetBuildFromSourceFlavor == Product -> DotNetBuildOrchestrator == true - Building in the VMR, could be source-only or MS's build.
- ArcadeBuildFromSource -> DotNetBuildRepo == true -> Indicates an outer repo build.
* Move to central package pinning
This should make it much easier for us to respond to CG alerts in the
future. All that will need to be done is add an entry in
Directory.Packages.props and it will automatically impact all consumers
of it.
Consider this example in Roslyn for how to respond to a CG issue
https://github.com/dotnet/roslyn/pull/74653
* Update dependencies from https://github.com/dotnet/arcade build 20240702.2
Microsoft.SourceBuild.Intermediate.arcade , Microsoft.DotNet.Arcade.Sdk
From Version 8.0.0-beta.24352.1 -> To Version 9.0.0-beta.24352.2
* Install .NET 8 runtime
* Update dependencies from https://github.com/dotnet/arcade build 20240702.2
Microsoft.SourceBuild.Intermediate.arcade , Microsoft.DotNet.Arcade.Sdk
From Version 8.0.0-beta.24352.1 -> To Version 9.0.0-beta.24352.2
* Disable BuildWithNetFrameworkHostedCompiler
---------
Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Co-authored-by: Jan Jones <janjones@microsoft.com>
Stop building no longer shipping net7 build
With the move for rzls to publish net8 binaries, we no longer use our net7 build. Remove the TFM from our builds (should speed CI builds)
Similar to the Microsoft.Net.Compilers.Toolset package that we use in roslyn, this nuget package will override the generators used by a project, replacing them with the specific versions from this package. The purpose of this package is to allow shipping hotfixes to customers directly in a simple manner, without having to ask them to manually do a bunch of msbuild magic or replacing existing dlls. It may be helpful to reference the targets that add the razor generators to the compilation in the first place when reviewing: https://github.com/dotnet/sdk/blob/main/src/RazorSdk/Targets/Microsoft.NET.Sdk.Razor.SourceGenerators.targets#L15.
Since integrating our repos, there have been a number of changes in PRs that touch the encoding of the file, adding or removing a BOM as the editor in question decides. I've standardized on UTF-8 with BOM, as we do in roslyn, and put it in the .gitattributes so it should hopefully stay consistent.
* Add sln filter for source build
* Use ExcludeSourceBuild instead
* Put the correct default in 🤦♂️
* Don't include npm targets when all targets are suppressed
* Don't override arcade for test projects when building from source
* Use default source build jobs now we don't need node
- Arcade by default does the right thing supposedly for projects & publishing symbols. We were holistically swapping debug types / setting if we should publish windows pdbs. Arcade now supports all of this by default so this is an attempt at resolving #6239 in hopes that arcade does the right thing.
- Updated repo NOTICE.txt to mention latest third party components.
- Removed individual component NOTICE.txt files. Instead all platforms now ship the same NOTICE.txt so we don't need to keep updating it everywhere.
- Added NOTICE.txt to Razor langauge server
- Added NOTICE.txt to Razor addin
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1531325
- We no longer track the Roslyn compiler separate from Arcade. This means we can have the latest C# features earlier when Arcade updates.
- Removed `<LangVersion>` specifications because we can rely on `Latest` everywhere now.
- Updated .editorconfig so new files have appropriate MIT license attached.
- Updated MSBuild license expression MSBuild info
- Updated License
- Did a find and replace on all other source files for `Apache License, Version 2.0` -> `MIT license`
Fixesdotnet/aspnetcore#34960
[master] Update dependencies from dotnet/arcade dotnet/aspnetcore
- Coherency Updates:
- Microsoft.Extensions.Configuration.Json: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.Extensions.Logging: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- System.Diagnostics.DiagnosticSource: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- System.Resources.Extensions: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- System.Text.Encodings.Web: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.Extensions.DependencyModel: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.App.Ref: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.App.Internal: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.App.Runtime.win-x64: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- Microsoft.NETCore.Platforms: from 6.0.0-alpha.1.20507.4 to 6.0.0-alpha.1.20525.3 (parent: Microsoft.CodeAnalysis.Razor)
- Merge branch 'master' into darc-master-7f5d6927-fec8-4156-805b-6521c68ceb00
- Transplant BenchmarkRunner sources from dotnet/aspnetcore
- Update BenchmarkDotnet package version
- latest version on NuGet.org
- also what we're using in dotnet/aspnetcore
- compatible with transferred `BenchmarkRunner` sources