Open
Conversation
Closed
Contributor
Author
|
Great work on #46 with updating to Blazor 3.0.0-preview5! I've updated this pull request with those dependencies. |
b2b39f0 to
6954baa
Compare
c26486c to
cf7af92
Compare
xperiandri
approved these changes
Jun 15, 2023
Contributor
|
Maybe move to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I believe that updating to newer versions of Blazor #38 will be much easier to do with NuGet PackageReferences than with Paket. NuGet has supported transitive dependencies since the new project format came out. It simplifies things significantly. But what about lock files. I can add lock files too now with NuGet 5.0 when wanted.
I ported everything over directly from the paket.references as a working first step.