forked from microsoft/playwright-dotnet
-
Notifications
You must be signed in to change notification settings - Fork 3
Closed
Labels
feature-parityIssues tracking feature parity with upstream PlaywrightIssues tracking feature parity with upstream Playwrightphase-1Phase 1: InfrastructurePhase 1: Infrastructure
Description
Description
Update all .csproj files to target net10.0, upgrade NuGet packages (xunit 2.9+, Microsoft.NET.Test.Sdk 17.x), remove net48/netcoreapp3.1 targets, and update LangVersion to latest.
What to Implement
- Update
TargetFrameworkin all .csproj files fromnetcoreapp3.1/net48/netstandard2.0tonet10.0(ornetstandard2.1for Abstractions) - Update
LangVersiontolatestor13across all projects - Upgrade NuGet packages:
- xunit to 2.9+
- Microsoft.NET.Test.Sdk to 17.x
- Other dependencies to latest compatible versions
- Fix any breaking changes from the framework upgrade
- Ensure the solution builds cleanly
Files to Modify
src/PlaywrightSharp.Abstractions/PlaywrightSharp.Abstractions.csprojsrc/PlaywrightSharp.Chromium/PlaywrightSharp.Chromium.csprojsrc/PlaywrightSharp.Firefox/PlaywrightSharp.Firefox.csprojsrc/PlaywrightSharp.Webkit/PlaywrightSharp.Webkit.csprojsrc/PlaywrightSharp.Tests/PlaywrightSharp.Tests.csprojsrc/PlaywrightSharp.TestServer/PlaywrightSharp.TestServer.csproj- Any other .csproj files in the solution
Verification
dotnet build ./src/PlaywrightSharp.sln
dotnet test ./src/PlaywrightSharp.Tests/PlaywrightSharp.Tests.csproj --filter Category=chromium -c Debug -f net10.0Dependencies
None — this is the foundational issue.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
feature-parityIssues tracking feature parity with upstream PlaywrightIssues tracking feature parity with upstream Playwrightphase-1Phase 1: InfrastructurePhase 1: Infrastructure