-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove code migrated to aspnetcore #1933
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't aware those need to be migrated. I'll handle those in a mop up. |
@NTaylorMullen I can move RazorSyntaxGenerator but the benchmarks project depends on Microsoft.CodeAnalysis.Razor.Workspaces. Does it mean that we need to move both of those? |
Also, where should the benchmarks move to in aspnetcore? Based on the naming, it would probably be src/Razor/Razor/perf/ but the rest of the projects under src/Razor/Razor were already in aspnetcore and doesn't have much to do with the benchmarks project, so I think src/Razor/perf might make more sense. Thoughts? |
...Razor/src/Microsoft.VisualStudio.Mac.RazorAddin/Microsoft.VisualStudio.Mac.RazorAddin.csproj
Outdated
Show resolved
Hide resolved
...osoft.VisualStudio.LanguageServices.Razor/ProjectSystem/Rules/RazorGenerateWithTargetPath.cs
Outdated
Show resolved
Hide resolved
Ahh, we may need to split the benchmarks into two. One for aspnetcore and one for aspnetcore-tooling. I don't want to have
Makes perfect sense to me!
We only include the pdbs in the mpacks which might prove to a point of concern in this migration. |
8ea6d87
to
4707905
Compare
I'll need to ingest newer packages and pdbs from aspnetcore when they are available, but otherwise the PR is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To finish this off, suggest running `darc update-dependencies --source-repo dotnet/aspnetcore --channel '.NET 5 Dev' while in this branch locally. If that doesn't do what you expect, fix it 😺 Otherwise, you've preemptively done the first Maestro++ update for the flow you can add after this PR is merged.
src/Razor/src/Microsoft.VisualStudio.Editor.Razor/LegacyProjectEngineFactory_1_0.cs
Show resolved
Hide resolved
...oft.VisualStudio.LanguageServices.Razor/Microsoft.VisualStudio.LanguageServices.Razor.csproj
Outdated
Show resolved
Hide resolved
...Razor/src/Microsoft.VisualStudio.Mac.RazorAddin/Microsoft.VisualStudio.Mac.RazorAddin.csproj
Outdated
Show resolved
Hide resolved
...Razor/src/Microsoft.VisualStudio.Mac.RazorAddin/Microsoft.VisualStudio.Mac.RazorAddin.csproj
Outdated
Show resolved
Hide resolved
...Razor/src/Microsoft.VisualStudio.RazorExtension/Microsoft.VisualStudio.RazorExtension.csproj
Outdated
Show resolved
Hide resolved
To be clear
Don't do this until this PR is merged. Also, delete the disabled aspnetcore-tooling -> aspnetcore edge for the 'master' branch now or at the same time. aspnetcore shouldn't need anything from here. If it does, that's a bug to fix before merging this PR. |
da7ec3d
to
de9454c
Compare
Needs another look @NTaylorMullen @dougbu I've addressed feedback items and updated to consume the latest aspnetcore packages. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed this by only looking at the modified files, assuming that the deleted files will have mirrored adds in dotnet/aspnetcore. Looks good. For a change of this magnitude I think it makes sense we wait for multiple approvals though.
|
I did 😄, I've addressed feedback items and updated to consume the latest aspnetcore packages. |
Oh actually @JunTaoLuo you should remove the testapps folder: And update the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I reviewed this by only looking at the modified files, assuming that the deleted files will have mirrored adds in dotnet/aspnetcore. Looks good. For a change of this magnitude I think it makes sense we wait for multiple approvals though.
+1
@NTaylorMullen I was under the impression a lot of the apps are still used elsewhere e.g. https://github.com/dotnet/aspnetcore-tooling/blob/master/src/Razor/test/VSCode.FunctionalTest/tests/TestUtil.ts#L15-L19 so I elected to keep all the tests apps. I can do a more granular check and remove ones that are not referenced I suppose. |
Ooh ya look at that. You've learned more about the tooling repo now then I have 😆 |
b3aed5b
to
ef0ff38
Compare
eng/Version.Details.xml
Outdated
<Uri>https://github.com/dotnet/aspnetcore</Uri> | ||
<Sha>a799bf68e45c63e62060a7916ebb6d4f87a9aa1b</Sha> | ||
</Dependency> | ||
<Dependency Name="Microsoft.Extensions.Configuration.Json" Version="5.0.0-preview.6.20277.12" CoherentParentDependency="Microsoft.CodeAnalysis.Razor"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is very weird and is not coherent with the dotnet/aspnetcore 5.0.0-preview.6.20278.12 build. We also don't want to downgrade these dependencies. Suspect you need to run darc update-dependencies --coherency-only
after we get dotnet/aspnetcore#1947 in.
@mmitche @wtgodbe the dotnet/aspnetcore is using dotnet/runtime dependencies at 5.0.0-preview.6.20271.10 at the a799bf6 commit. Why didn't CoherentParentDependency
do the "correct" thing and back up all that way? We don't really want to downgrade at all but that at least would have been coherent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It did the expected thing when I ran it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean it downgraded to 5.0.0-preview.6.20271.10?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, I pointed to the wrong dependency update PR.
@JunTaoLuo only just added an arc updating dotnet/aspnetcore directly from dotnet/runtime. I triggered it moments ago. This PR won't be ready to go (really, the dependencies won't be coherent without downgrading) until dotnet/aspnetcore#22370 and the subsequent official build and Maestro++ update are done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JunTaoLuo you've got lots of approval here but please don't merge until you're able to update the dependencies in this branch correctly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, it downgraded locally. What's the darc version that got used to do that update? Seems unlikely that would affect things but could be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Locally for me, darc doesn't seem to do any coherency updates, but it could be because aspnetcore hasn't ingested newer runtime versions yet. I'm waiting to confirm that once the runtime update in aspnetcore is merged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Triggered a subscription update and looks like the latest commit shows that updates are working as expected.
Also remove RazorPageGenerator
- remove CodeAnalysis.Razor.Tests - remove source build step
de22ef7
to
18ac899
Compare
…0200529.12 (#1951) Microsoft.NET.Sdk.Razor , Microsoft.CodeAnalysis.Razor , Microsoft.AspNetCore.Razor.Internal.Transport , Microsoft.AspNetCore.Razor.Language , Microsoft.AspNetCore.Mvc.Razor.Extensions.Version2_X , Microsoft.AspNetCore.Mvc.Razor.Extensions.Version1_X , Microsoft.AspNetCore.Mvc.Razor.Extensions From Version 5.0.0-preview.6.20278.12 -> To Version 5.0.0-preview.6.20279.12 Dependency coherency updates Microsoft.Extensions.Configuration.Json,Microsoft.Extensions.Logging,System.Diagnostics.DiagnosticSource,System.Resources.Extensions,System.Text.Encodings.Web,Microsoft.Extensions.DependencyModel,Microsoft.NETCore.App.Ref,Microsoft.NETCore.App.Internal,Microsoft.NETCore.App.Runtime.win-x64,Microsoft.NETCore.Platforms From Version 5.0.0-preview.6.20277.12 -> To Version 5.0.0-preview.6.20278.9 (parent: Microsoft.CodeAnalysis.Razor Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
Woooo!! |
TODO after dotnet/aspnetcore#21581 is merged: