Case insensitive doesn't exist in postgres.
For te search is a problem, please use citext extensions instead text foreach type string.
npgsql/efcore.pg#236
https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/providers#one-migration-set

FTP OS: Unix

FTP Server: ProFTPD

Computer OS: Windows 10

Many functions result in Socket-related issues.

Logs :

<paste logs here but DO 

The lack of documentation is surprising, I'm new to all of this so It confuses me alot how to even beginn a project.
Could someone have a look and verify which modules need to be installed for a minimal Qml.Net to work, And add this to a wiki?

Additional Questions:
Does Visual Studio need all these C++ dependencies if QT have them?
Is there a way to simple choose between MSVC and MinGW

Is your feature request related to a problem? Please describe.
In the documentation you simply pass an IQueryable to the PagedList without any sort of keyselector. However if you e.g. pass an IQueryable from a database without any keyselector, then the results aren't guaranteed.

The generated SQL (For sql server) is as follows

SELECT [a].[WtgId], [a].[TimeOnUtc], [a].[Code], [a]

Hello,

I'm looking for any documentation about this library ? The example is a bit short.

There is no explication about settings (for example "Page","ViewportSize" etc in Global and ObjetSettings :(

Anyone interested in creating a documentation ?

Command types should not contain options that resolve to one of the built-in options, i.e. --help/-h and --version (only on default command).

Currently this is not validated and will lead to undefined behavior (built-in options take precedence but both kind of options will still appear in help text).

Need to add validation and corresponding tests.

There's no install bat in the root of the directory.
There's no instructions in the readme.
There's a bunch of sln projects, but all for old vs versions, so not sure which one to use.

Gaaarh

Added in #173

It would be good to add:

• comments in the code
• some samples to the repo

Bug

NLog version: 4.6.8
NLog.Extensions.Logging version: 1.6.1
NLog.Web.AspNetCore version: 4.9.0

Platform: .NET Core 3.2
Current NLog config

<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      autoReload="true"
      internalLogLevel="In

It's currently only referenced as a nupkg package without any documentation on how to use it. The goal of this project is to help developers adopt fido2, we should therefore add proper documentation.

When logging, there would be times where you'd like to know whether the exception was one configured.

Example:

x.OnError((context, exception, httpContext) =>
{
    if (!context.wasCaught){
        _logger.Error(exception.Message);
    }
    return Task.CompletedTask;
});

update documentation on:

Running under the full IIS

dotnet/AspNetCore.Docs#1982 (comment)
https://docs.asp.net/en/latest/publishing/iis.html
https://msdn.microsoft.com/magazine/mt736459
aspnet/Announcements#172
https://www.strathweb.com/2015/12/running-asp-net-5-website-on-iis/

HTTPs

https://blogs.msdn.microsoft.com/webdev/2017/11/29/c