Skip to content

Commit c18cecf

Browse files
committed
Updating .NET CHANGELOG for pending 3.9.0 release
1 parent cba535b commit c18cecf

File tree

1 file changed

+31
-0
lines changed

1 file changed

+31
-0
lines changed

dotnet/CHANGELOG

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,34 @@
1+
v3.9.0
2+
======
3+
* Added commands to get and set network conditions for Chrome in .NET.
4+
To get or set the network conditions, use the `NetworkConditions` property
5+
of the ChromeDriver object. This property gets or sets a
6+
ChromeNetworkConditions object which contains the proper values. Fixes
7+
issue #5338.
8+
* Readded CLSCompliant attribute to .NET assemblies. When converting from
9+
the prior build system to using Buck and the dotnet build tools, the
10+
assembly-level CLSCompliant attribute was removed. This commit restores
11+
the CLSCompliant attribute to the assembly manifests. Fixes issue #5324.
12+
* Removed check for leading hyphens in .NET FirefoxOptions AddArgument.
13+
In prior releases of geckodriver, it was a requirement that all arguments
14+
be preceeded by double hyphens ("--"). Geckodriver has now relaxed that
15+
restriction, and the .NET bindings need to keep up with that change. This
16+
commit removes the check for leading hyphens when calling AddArgument.
17+
* Fixed strong-named assembly references. In the move to using the `dotnet`
18+
build tools instead of calling the C# compiler directly, the creation of
19+
strong-named assemblies was broken with incorrect references being created.
20+
This commit fixes that problem. Fixes issue #5254.
21+
* Exposed HostName property for .NET DriverService class. Previously, the
22+
host name for a DriverService was hard-coded to be "localhost." This is
23+
normally acceptable, as a DriverService is only intended to be used
24+
locally, and most executables that are represented by a DriverService
25+
(chromedriver, geckodriver, IEDriverServer.exe, etc.) do not even allow
26+
connections from external machines for security reasons. However, there is
27+
a legitimate use case (.NET Standard 2.0) where a local IP address
28+
("127.0.0.1" or "::1") is preferrable to using the "localhost" moniker.
29+
This HostName property allows the user to specify that IP address. Note
30+
that the property defaults to "localhost," preserving previous behavior.
31+
132
v3.8.0
233
======
334
* Updating .NET bindings setting of timeouts for spec-compliance. This

0 commit comments

Comments
 (0)