Граф коммитов

25 Коммитов

Автор SHA1 Сообщение Дата
Matt Mitchell ca91065e45
Switch to new VMR control schema. (#10883)
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.
2024-09-13 17:32:10 +00:00
Andrew Hall 9acd5266cc
Allow multiple forms for the featureflag script (#10304)
It was tedious to get the actual argument right, so this checks for multiple forms and tries to correct them.

The following should be supported now:

eng\scripts\featureflag.ps1 -set -flag Razor.LSP.ForceRuntimeCodeGeneration -enable
eng\scripts\featureflag.ps1 -set -flag Razor\LSP\ForceRuntimeCodeGeneration -enable
eng\scripts\featureflag.ps1 -set -flag FeatureFlags.Razor.LSP.ForceRuntimeCodeGeneration -enable
eng\scripts\featureflag.ps1 -set -flag FeatureFlags\Razor\LSP\ForceRuntimeCodeGeneration -enable

This should make copying the value from code easier to figure out. We could also just assume feature flags start with FeatureFlags\LSP\Razor\<flagname> but that's not inherantly true, just happens to be for now.
2024-04-24 14:17:59 -07:00
David Wengier 5718047148 It's not YAML, but I'm equally bad at it 2024-04-23 14:14:06 +10:00
David Wengier a99aa8204f Fix powershell script 2024-04-23 13:33:04 +10:00
David Wengier 8608c845c5 Output VS version info 2024-04-23 11:40:08 +10:00
Andrew Hall 155484bce6 Fix the feature flag script to correctly use vsRegEdit 2024-04-03 17:45:17 -07:00
Andrew Hall 416d1fd658
Make it possible to set featureflags during integration test runs (#10195) 2024-04-01 23:56:29 +00:00
Fred Silberberg fcae93171c
Update file encoding to UTF-8 with BOM (#8099)
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.
2023-01-10 01:57:58 +00:00
Ryan Brandenburg d959ee5799 Newline 2022-10-28 11:26:41 -07:00
Ryan Brandenburg 3a1d440852 Parameterize 2022-10-28 11:24:00 -07:00
Ryan Brandenburg adc1a5cea3 Retry hive creation and move to script 2022-10-28 11:18:37 -07:00
Dustin Campbell bba4cb0ad0 Tweak the dump collection scripts a bit 2022-10-27 11:10:29 -07:00
David Wengier 1120c6fce1 PR Feedback 2022-10-25 11:59:29 +11:00
Doug Bunting 46b62c1677
Master to main (#3310)
- this repo as well as arcade, roslyn and a few others
2021-03-19 17:30:20 -07:00
Doug Bunting e759982cb6 Ignore error output from `Get-Process`
- allow FinishDumpCollectionForHangingBuilds.ps1 to complete w/o writing to `stderr`

nit: copy a typo fix from aspnetcore
2020-05-15 16:59:09 -07:00
Kevin Pilch fae9a5fdbc
Update links for repo moves/renames (#1474) 2020-01-08 16:51:55 -08:00
John Luo 1861777002 Fix source build 2019-11-27 22:56:17 -08:00
N. Taylor Mullen e980416506 Merge branch 'nimullen/13494.prereq' into release/3.1 2019-09-20 11:46:12 -07:00
N. Taylor Mullen dddbc14893 Add support for npmproj.
- In preparation for merging the Razor VSCode extension I've added support for npmproj files. I tried to maintain the same functionality that AspNetCore offers for its npmproj support.
- Added an extra `--ignore-engines` check to `yarn install` in preparation for VSCode's extension model. They expect there to be a vscode engine in the package.json that yarn doesn't understand.

aspnet/AspNetCore#13494
2019-09-20 11:44:08 -07:00
Javier Calvarro Nelson a9b7e24791
[Infrastructure] Install procdump and capture dumps on build hangs (#1146)
* Captures process dumps when the build hangs.
* Captures process dumps when a child process hangs inside a test.
2019-09-19 18:36:02 +02:00
John Luo 133b252f09
Support netcoreapp3.1 TFM (#1122)
* Support netcoreapp3.1 TFM

* Update branding to preview1

* Skip failing 1.1 test
2019-09-12 22:02:18 -07:00
Nate McMaster 986c224acf
Add support for source-build (#620) 2019-05-29 13:06:38 -07:00
Nate McMaster 202d5fed8a
Filter non-project output from `dotnet sln list` (#228)
Workaround https://github.com/dotnet/cli/issues/10845

Apparently DOTNET_SKIP_FIRST_TIME_EXPERIENCE does not actually skip the initial welcome message output.
2019-02-20 08:35:13 -08:00
Nate McMaster 182b2c81a5
Suppress the 'Welcome to .NET Core!' output that breaks invocations of `dotnet sln` 2019-02-19 12:44:02 -08:00
Nate McMaster 6645ec6a80
Update dependencies and add a code check step to PR validation (#217)
Changes:
* Update to latest core-setup dependencies (generated using https://github.com/aspnet/AspNetCore-Internal/pull/1830)
* Add a step which asserts that version.props and versions.details.xml are in sync
* Add PR check which ensures solution files are not broken
2019-02-19 09:17:05 -08:00