[dotnet] Align CS projects name to understand the editing context

[nvborisenko]

User description

🔗 Related Issues

Resolves #15823

💥 What does this PR do?

Adjust naming in .NET to understand what I am editing.

🔧 Implementation Notes

💡 Additional Considerations

🔄 Types of changes

• Cleanup (formatting, renaming)

---

PR Type

Enhancement

---

Description

• Renamed .NET solution and project files for clarity

  • WebDriver.csproj to Selenium.WebDriver.csproj
  • WebDriver.Support.csproj to Selenium.WebDriver.Support.csproj
  • Test project files similarly renamed for all browsers

• Updated project references and solution file to match new names

• Added and updated .nuspec files for renamed projects

• Cleaned up and standardized test project files and references

---

Changes walkthrough 📝

	Relevant files
Configuration changes	18 files Selenium.WebDriver.sln Update solution to reference renamed project files              +10/-10  Selenium.WebDriver.Support.csproj Update support project reference to new WebDriver name      +1/-1      Selenium.WebDriver.Common.Tests.csproj Update reference to renamed WebDriver project                        +1/-1      Selenium.WebDriver.Chrome.Tests.csproj Add renamed Chrome test project file                                          +18/-0    WebDriver.Chrome.Tests.csproj Remove old Chrome test project file                                            +0/-38    Selenium.WebDriver.Chrome.Tests.nunit Add NUnit config for renamed Chrome tests                                [link]    Selenium.WebDriver.Edge.Tests.csproj Update Edge test project to use new references                      +2/-21    Selenium.WebDriver.Edge.Tests.nunit Add NUnit config for renamed Edge tests                                    [link]    Selenium.WebDriver.Firefox.Tests.csproj Update Firefox test project to use new references                +2/-20    Selenium.WebDriver.Firefox.Tests.nunit Add NUnit config for renamed Firefox tests                              [link]    Selenium.WebDriver.IE.Tests.csproj Update IE test project to use new references                          +2/-17    Selenium.WebDriver.IE.Tests.nunit Add NUnit config for renamed IE tests                                        [link]    Selenium.WebDriver.Remote.Tests.csproj Update Remote test project to use new references                  +2/-17    Selenium.WebDriver.Remote.Tests.nunit Add NUnit config for renamed Remote tests                                [link]    Selenium.WebDriver.Safari.Tests.csproj Update Safari test project to use new references                  +2/-12    Selenium.WebDriver.Safari.Tests.nunit Add NUnit config for renamed Safari tests                                [link]    Selenium.WebDriver.Support.Tests.csproj Update Support test project to use new references                +4/-18    Selenium.WebDriver.Support.Tests.nunit Add NUnit config for renamed Support tests                              [link]
Enhancement	5 files Selenium.WebDriver.csproj Add renamed main WebDriver project file                                    [link]    Selenium.WebDriver.nuspec Add nuspec for renamed WebDriver package                                  [link]    Selenium.WebDriver.StrongNamed.nuspec Add nuspec for strong-named WebDriver package                        [link]    Selenium.WebDriver.Support.nuspec Add nuspec for renamed Support package                                      [link]    Selenium.WebDriver.Support.StrongNamed.nuspec Add nuspec for strong-named Support package                            [link]
Additional files	1 files Selenium.WebDriver.snk [link]

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[selenium-ci]

Thank you, @nvborisenko for this code suggestion.

The support packages contain example code that many users find helpful, but they do not necessarily represent
the best practices for using Selenium, and the Selenium team is not currently merging changes to them.

We actively encourage people to add the wrapper and helper code that makes sense for them to their own frameworks.
If you have any questions, please contact us

[qodo-merge-pro]

PR Reviewer Guide 🔍

(Review updated until commit fea13ba)

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 15823 - Fully compliant Compliant requirements: Rename WebDriver.NET.sln to Selenium.WebDriver.sln Rename WebDriver.csproj to Selenium.WebDriver.csproj Rename WebDriver.Support.csproj to Selenium.WebDriver.Support.csproj Rename test project files to follow the same naming pattern

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Project References The InternalsVisibleTo attribute still references the old project name "WebDriver.Common.Tests" instead of the new name pattern. <InternalsVisibleTo Include="WebDriver.Common.Tests" /> </ItemGroup>

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Update assembly file paths The file paths in the nuspec file should be updated to match the new naming convention. Since the project is being renamed to include "Selenium" prefix, the assembly names in the file paths should be updated accordingly. dotnet/src/support/Selenium.WebDriver.Support.StrongNamed.nuspec [34-36] -<file src="lib/netstandard2.0/WebDriver.Support.StrongNamed.dll" target="lib/netstandard2.0/WebDriver.Support.StrongNamed.dll" /> -<file src="lib/netstandard2.0/WebDriver.Support.StrongNamed.pdb" target="lib/netstandard2.0/WebDriver.Support.StrongNamed.pdb" /> -<file src="lib/netstandard2.0/WebDriver.Support.StrongNamed.xml" target="lib/netstandard2.0/WebDriver.Support.StrongNamed.xml" /> +<file src="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.dll" target="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.dll" /> +<file src="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.pdb" target="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.pdb" /> +<file src="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.xml" target="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.xml" /> Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies an inconsistency where assembly file paths still use the old WebDriver.Support.StrongNamed naming while the PR consistently renames projects to include the Selenium prefix. This could cause packaging issues.	Medium
Update

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Update assembly file paths The file paths in the nuspec file should be updated to match the new naming convention. Since the project is being renamed to include "Selenium" prefix, the assembly names in the file paths should be updated accordingly. dotnet/src/support/Selenium.WebDriver.Support.StrongNamed.nuspec [34-36] -<file src="lib/netstandard2.0/WebDriver.Support.StrongNamed.dll" target="lib/netstandard2.0/WebDriver.Support.StrongNamed.dll" /> -<file src="lib/netstandard2.0/WebDriver.Support.StrongNamed.pdb" target="lib/netstandard2.0/WebDriver.Support.StrongNamed.pdb" /> -<file src="lib/netstandard2.0/WebDriver.Support.StrongNamed.xml" target="lib/netstandard2.0/WebDriver.Support.StrongNamed.xml" /> +<file src="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.dll" target="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.dll" /> +<file src="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.pdb" target="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.pdb" /> +<file src="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.xml" target="lib/netstandard2.0/Selenium.WebDriver.Support.StrongNamed.xml" /> Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies an inconsistency where assembly file paths still use the old WebDriver.Support.StrongNamed naming while the PR consistently renames projects to include the Selenium prefix. This could cause packaging issues.	Medium
More

[nvborisenko]

TODO: review post usage like release.

[nvborisenko]

Looks good to me:

[titusfortner]

wouldn't people need to change the dependencies in their code from this? Maybe we could make this change for 5.0, but even then we'd end up stranding a lot of people who don't really pay attention, and even if it makes the name more clear, I don't think it is worth that outcome.

[nvborisenko]

No impact for end users, fully backward compatible. It is only about us, for maintainers. These changes reflect the project structure better. When I have many IDE instances opened, now I can easily understand what project links to nuget package. Probably the name is longer, but it is really better (at least 2 people agreed from .NET world independently, see related issue).