-
Updated
May 10, 2022 - C#
netcore
Here are 2,810 public repositories matching this topic...
-
Updated
May 9, 2022 - C#
-
Updated
May 11, 2022 - C#
-
Updated
May 10, 2022 - C#
-
Updated
Apr 13, 2022 - C#
-
Updated
May 7, 2022 - C#
-
Updated
May 9, 2022 - C#
Bug type
Other
Component name
No response
What happened?
The enum value OverflowBehavior.FilpOnOpen works. The correct spelling OverflowBehavior.FlipOnOpen does not.
Expected behavior
Rename the value to OverflowBehavior.FlipOnOpen
Reproduction link
https://github.com/MudBlazor/MudBlazor/blob/dev/src/MudBlazor/Enums/OverflowBehavior.cs
Reproduction steps
Consider the following F# code
open System
[<Obsolete("Foo", true)>]
type Foo() =
member _.Bar() = ()
let foo = Foo()
foo.Bar()It compiles just fine, regardless the ObsoleteAttribute on the type. It won't produce a diagnostic even if we call to foo.Bar() [[SharpLab](https://sharplab.io/#v2:DYLgZgzgNALiBOBXAdgHwPYAcCmyAEAygJ4QzYC2AsAFA0DaAPAPIBGE6w2ZAFAEQBi6d
-
Updated
May 8, 2022 - C#
It is currently a pain to use an OxyPlot.WinfowsForms.PlotView with a transparent background: it throws if you set its BackColor to transparent. To avoid this, it is necessary to set the ControlStyles.SupportsTransparentBackColor style to true on the PlotView; however, Control.SetStyle is protected, so consumers must resort to reflection or extending PlotView to do so. This could be
-
Updated
May 10, 2022 - C#
Improve BruteShark performance by refactor the BLL layer (aka PcapAnalyzer project to use multi thread mechanism).
That includes:
- Design the solution and discuss about it with me.
- Implement it.
- Writing tests that will test exactly this mechanism.
-
Updated
May 8, 2022 - C#
-
Updated
Mar 25, 2022 - C#
-
Updated
Mar 7, 2022 - C#
Bug Report
If you use the B3 propagator with e.g. the Grpc.Core instrumentation then it fails to connect the parent spans to the new server spans because gRPC headers are always lower case.
The issue is that the B3 propagator does not store the headers as lower case and then this line in the Grpc.Core instrumentation does not do case-insensitive comparison: https://github.com/open-telemetry/
-
Updated
May 11, 2022 - C#
-
Updated
Apr 23, 2022 - C#
-
Updated
Apr 28, 2022 - C#
-
Updated
May 10, 2022 - C#
-
Updated
Apr 29, 2022 - C#
-
Updated
May 10, 2022 - C#
-
Updated
May 10, 2022 - C#
Version: MSAL.NET @ 4.42
Platform: Windows 11, net5.0-windows10.0.17763.0
Auth flow: Broker and Interactive Web auth (embedded web view only)
Repro
@bgavrilMS - we have an easy repro internally and a current bugfix in the auth CLI.
private class MsalHttpClientFactoryAdaptor : IMsalHttpClientFactory
{
private HttpClient instance;
publicImprove this page
Add a description, image, and links to the netcore topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the netcore topic, visit your repo's landing page and select "manage topics."
Discussed in SixLabors/ImageSharp#2061
Originally posted by br3aker March 13, 2022
Current jpeg implementation lacks of COM marker support, does it need to support it? Should be easy to implement as this marker is just an array of bytes - itu spec leaves 'interpretation to the application', decoding API shoul