Thomas Bolon

Maybe you should add FileZilla Server on windows ? | FTP software | Platform | Bits | Architecture | ------------------ | ------- | --- | --------- | | FileZilla Server...

I have also noted that TLS 1.3 is not officially supported on [.net versions prior 5.0](https://github.com/dotnet/runtime/issues/47457#issuecomment-767669971) or only on Win11, and there are multiple articles regarding TLS 1.3 support on...

I have also created a discussion on [FileZilla Server Support Forum](https://forum.filezilla-project.org/viewtopic.php?f=6&t=54575&p=180065#p180065) and got replies from the developer of FileZilla. I also have forked FluentFTP to create a simple program app...

Please also note that when using Windows 10, FluentFTP could not even connect to the server: ``` [Verbose] > Connect() [Info] Status: Connecting to ::1:21 [Verbose] Response: 220-FileZilla Server 1.3.0...

You are right, it seems to be a bug in SChannel itself. I will continue to track this issue and report any progress here.

FYI, in my case I am planning to write a .NET wrapper around the hurl process, which launch the hurl process then parse output. But in my case I will...

Why not using environment variables ? Having hurl auto-injecting variables prefixed with a constant suffix (HURL_xxx) ?

I am trying to resurrect this issue, linking to my [other opentelemetry issue](https://github.com/open-telemetry/opentelemetry-dotnet/issues/1900). The goal are similar and still the same: we want to register redis instrumentation when configuring OpenTelemetry...

Everything makes perfect sense. There is also the case of metrics, which makes a lot more sense in my opinion regarding commands, see https://docs.microsoft.com/en-us/dotnet/core/diagnostics/metrics-instrumentation. See how an open telemetry receiver...

> For adapting, [SqlClient is ultimately starting an Activity](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Instrumentation.SqlClient/Implementation/SqlClientDiagnosticListener.cs#L60). This incurs quite a bit of overhead per command vs. our `Message` today. Per overhead, there is only one method call...