netcore

A follow up on SixLabors/ImageSharp#1378 (comment).

Currently 32 bit test execution is only done for .NET Framework, with dotnet xunit which is an obsolete tool today, we need to adapt dotnet test, and add 32 bit CI targets for both net5.0 and netcoreapp3.1. Opening an issue to remember and track this debt.

See:
https://twitter.com/tannergooding/s

Bug type

Component

Component name

MudLink, MudButton

What happened?

Link and Href parameters both function as a mean to generate <a href="#"></a> elements.

<MudButton Link="#">Go</MudButton>
<MudLink Href="#">Go</MudLink>

Names of these parameters should be unified across components.

Expected behavior

<MudButton Link="#">G

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

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.

It looks like a good amount of time is spent on nuget restore. And majority of them from the example projects, which are not required for all the build/test pipelines. We may benefit, if examples are built in a dedicated pipeline, and ignored by other pipelines.