Best Of

Turning off "Smart App Control" solved the problem for me also. Thanks! 👍

Had the same problem on my new PC. Exclusions (alone) didn't help.

Smart App Control was the key - it was in Evaluation Mode. Disabling it resulted in my test execution times going from 400ms to <1ms with Defender enabled. Typically I see times around 0.2ms.

Regarding what Smart App Control is, here's the support article: https://support.microsoft.com/en-us/topic/what-is-smart-app-control-285ea03d-fa88-4d56-882e-6698afdb7003

Smart App Control adds significant protection from new and emerging threats by blocking apps that are malicious or untrusted. Smart App Control also helps to block potentially unwanted apps, which are apps that may cause your device to run slowly, display unexpected ads, offer extra software you didn't want, or do other things you don't expect.

Smart App Control works alongside your other security software, such as Microsoft Defender or non-Microsoft antivirus tools, for added protection.

What I gather from the article, developers are not great candidates for Smart App Control.

Essentially, we're looking to see if Smart App Control is going to get in your way too often. There are some legitimate tasks that corporate users, developers, or others may do regularly that may not be a great experience with Smart App Control running. If we detect during evaluation mode that you're one of those users, we'll automatically turn Smart App Control off so you can work with fewer interruptions.

I concluded that I can just disable it. Anyone on this forum also likely is in the same group of people.

Hope that helps.

It is so fitting that LINQPad is the poster child for Avalonia XPF:

@yossizahn - thanks. This should now be fixed in 8.101.5

I hope when LINQPad for macOS is released, it would be possible to ship it for macOS INTEL x64.

The first public preview of LINQPad for macOS is now available:
https://www.linqpad.net/LINQPad8Mac.aspx

Keep in mind that not all features have yet been implemented.

Let me know your thoughts!

The same license will work for both.

Replacing the Key/Value should be simple as long as you don't want to use spaces ( or other characters that C# does not allow in identifiers or start with a number)

You can just use

    d.Select(e => new { Classes = e.Key, Propriétés = e.Value}).Dump();

Replacing the header isn't as easy. You can get something that looks like

by using

d.Select(e => new { Classes = e.Key, Propriétés = e.Value }).Dump("Tableau de référencement des classes et des Propriétés");

You could use the tricks from https://forum.linqpad.net/discussion/3262/is-there-a-simple-way-to-hide-object-header-display-from-dump to remove the blue header but see the caveats in that thread.

The only way I know to get output like in your picture is a hack to use regex to parse the html produced by the dump command and replace the header. That obviously means that a LinqPad update could break the hack which may not be something you want. (I have done this in the past with a program that is running on a server and referenced LinqPad to create a free html tables that would be sent to myself via email. But because I was not running LinqPad directly, I knew it would not be updated and possibly break my hack)

If you want I can upload the script but it was just something thrown quickly thrown together.

@naile: That's right, it's just Apple silicon for now. It would actually end up being quite expensive to support Intel - everything would need to be tested twice. And having a single deployment with multiple launchers like in Windows doesn't fit well with the macOS application model, so there would need to be two deployments and two automatic update streams for macOS (4 counting the betas). Then there's all the native dependencies which will be different, and the hardware intrinsics in LINQPad's debugger.

This will be fixed in the next LINQPad 8 release.