The MvcShims defined in tooling are only refernced in the projects located in "src\Razor\test\testapps". However, those projects don't appear to actually ever be built by anything. The source files in the "testapps" projects are used by some of the tooling benchmarks, but that usage doesn't require us to continue building the shims.
* Reapply "Don't rebuild when doing rid-specific publishing, just publish (#9925)" (#10014)
This reverts commit c5c96a26b1.
* Slim down the built rids for vertical builds and only reduce overbuilding on a vertical build (where we won't have the other AppHost RIDs anyway).
Also re-enable building the language servers in VMR non-sourcebuild builds.
* Fix bad copy-paste job
* Just use the regular RuntimeIdentifier property as PublishRuntimeIdentifier doesn't seem like it wants to work nicely.
* fix typo
* Pass TargetRid differently
* PR feedback and preserve existing properties
* Don't rebuild when doing rid-specific publishing, just publish
Before this change, every transitive dependency of these projects were getting rebuilt for each specified RID in addition to the RIDless builds.
* Add rzls to the non-Windows solution filter so we build it (as now publish depends on the build having already happened)
* We were still publishing the razor server and telemetry packages in the dotnet/razor source-build leg, but they aren't included in the source-build intermediates and aren't used by any other portion of source-build. Additionally, they're already marked as `DotNetBuildFromSource != true`, so I believe the intent is to not publish them in source-build anyway.
* Make unittest reliable
Make RazorExtension the default project after clean
* Remove shared state from test class
* Maybe the dispatcher is busy in CI due to slower machines?
---------
Co-authored-by: David Wengier <david.wengier@microsoft.com>
* Add missing compiler tests and dependency projects to the solution filter
* Be RID-specific with asp.net framework testing reference.
* Update Roslyn versions, remove duplicate Moq versions
* Pipe through SuppressUniqueIds to remove checksums from test baselines
* Depend on roslyn test utilities, use their diagnostic verification.
* Add packagemappins
* Adjust more usings in Razor.Language tests.
* Update property name for consistency.
* Update comment wording.
* Route TestSuppressUniqueIds through a different path.
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.
With the introduction of Microsoft.AspNetCore.Razor.Utilities.Shared,
this assembly is no longer useful. The only types left in it were
in support telemetry, and those can easily be moved to
Microsoft.CodeAnalysis.Razor.Workspaces, which is already referenced by
most tooling projects. This will help reduce image loads in Visual
Studio.
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.
* Remove razor-compiler.sln from root directory
* Move Razor.sln and Razor.Slim.slnf into root directory
* Put all projects from razor-compiler.sln into Razor.sln, with same solution folder layout
* Fix builds and docs
* Remove a couple of redundant files in the src\Razor folder
Dustin Campbell
Jan Jones
Jeremy Koritzinsky
Andrew Hall
Phil Allen
Fred Silberberg
Allison Chou
David Wengier