Skip to content
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

Merged
merged 15 commits into from
May 30, 2020
Merged

Conversation

JunTaoLuo
Copy link
Contributor

@JunTaoLuo JunTaoLuo commented May 26, 2020

TODO after dotnet/aspnetcore#21581 is merged:

  • Fixup sln files
  • Invert darc subscription
  • Ingest packages from aspnetcore

Copy link
Contributor

@NTaylorMullen NTaylorMullen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to also migrate the benchmarks and syntax generator:
image

eng/Versions.props Show resolved Hide resolved
@JunTaoLuo
Copy link
Contributor Author

I wasn't aware those need to be migrated. I'll handle those in a mop up.

@JunTaoLuo
Copy link
Contributor Author

@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?

@JunTaoLuo
Copy link
Contributor Author

JunTaoLuo commented May 27, 2020

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?

@NTaylorMullen
Copy link
Contributor

@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?

Ahh, we may need to split the benchmarks into two. One for aspnetcore and one for aspnetcore-tooling. I don't want to have Microsoft.CodeAnalysis.Razor.Workspaces in aspnetcore. Currently the benchmarks only has a single file that depends on the Razor.Workspaces project so everything else can go.

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?

Makes perfect sense to me!

Hmm seems like pdbs are not included in nupkgs.

We only include the pdbs in the mpacks which might prove to a point of concern in this migration.

@JunTaoLuo
Copy link
Contributor Author

I'll need to ingest newer packages and pdbs from aspnetcore when they are available, but otherwise the PR is ready for review.

Copy link
Member

@dougbu dougbu left a 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.

@dougbu
Copy link
Member

dougbu commented May 29, 2020

To be clear

Invert darc subscription

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.

@JunTaoLuo JunTaoLuo force-pushed the johluo/remove-migrated-projects branch from da7ec3d to de9454c Compare May 29, 2020 09:42
@JunTaoLuo
Copy link
Contributor Author

Needs another look @NTaylorMullen @dougbu I've addressed feedback items and updated to consume the latest aspnetcore packages.

Copy link
Contributor

@ryanbrandenburg ryanbrandenburg left a 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.

@ryanbrandenburg
Copy link
Contributor

Needs another look @NTaylorMullen @dougbu I've addressed feedback items and updated to consume the latest aspnetcore packages.
I keep forgetting it exists, but GitHub has a "request re-review" button that's nice for this kind of thing. Sometimes it still makes sense to make a comment if you need to explain what has changed though.

@JunTaoLuo
Copy link
Contributor Author

Sometimes it still makes sense to make a comment if you need to explain what has changed though.

I did 😄, I've addressed feedback items and updated to consume the latest aspnetcore packages.

eng/Versions.props Show resolved Hide resolved
@NTaylorMullen
Copy link
Contributor

Oh actually @JunTaoLuo you should remove the testapps folder:
image

And update the .vscode/settings.json file to not boot to it

Copy link
Contributor

@TanayParikh TanayParikh left a 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

@JunTaoLuo
Copy link
Contributor Author

@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.

@NTaylorMullen
Copy link
Contributor

@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 😆

@JunTaoLuo JunTaoLuo force-pushed the johluo/remove-migrated-projects branch from b3aed5b to ef0ff38 Compare May 29, 2020 19:45
<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">
Copy link
Member

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.

Copy link
Member

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.

Copy link
Member

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?

Copy link
Member

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.

Copy link
Member

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.

Copy link
Member

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.

Copy link
Contributor Author

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.

Copy link
Contributor Author

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.

@JunTaoLuo JunTaoLuo force-pushed the johluo/remove-migrated-projects branch 2 times, most recently from de22ef7 to 18ac899 Compare May 30, 2020 08:25
…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>
@JunTaoLuo JunTaoLuo merged commit f2fab7a into master May 30, 2020
@JunTaoLuo JunTaoLuo deleted the johluo/remove-migrated-projects branch May 30, 2020 09:45
@NTaylorMullen
Copy link
Contributor

Woooo!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants