Best Of

Have they downloaded the wrong program?

As far as I know Linqer has nothing to do with LinqPad, so you are unlikely to get an authoritative answer here and it might be better to ask at https://sqltolinq.com/forum

It looks like the file \runtimes\win10-x64\nativeassets\net6.0-windows10\e_sqlite3.dll in the sqlitepclraw.lib.e_sqlite3\2.0.7 package is corrupt. If you overwrite it with the version from runtimes\win-x64\native, it works. Perhaps they could fix the corrupt file (or just remove it)?

Hi Joe,

Can't i buy LINQPad 5 anymore?
(I'm still going to use .NET Framework for a while!)

This probably a dim question, but if I have a table with a LOT of columns, is there anyway, if I've used Util.Pivot to order the subsequent rows (ie the fields from the table) alphabetically?

Love the Pivot option anyway, but there is always something else, right?

Your script is technically still running since you're using Control components that need to function after the script has completed (e.g., Button). To be able to run the component actions, something has to be running to execute them.

If you want to run it and have it completely stop, don't use UI controls like you are, just run the action code directly.

Looks like there's been a change in the format of the .runtimeconfig.json file that's generated for ASP.NET applications.

Try the 7.2.6 beta - it should resolve the problem.
https://www.linqpad.net/LINQPad7.aspx#beta

Not sure how to explain this on how or why it happens, but every once in a while, the entire linqpad interface will freeze, usually while running a script. If I remember correctly, you can still scroll the windows (no you can't), but clicking on anything or typing does absolutely nothing. It will be come responsive again if you are able to minimize the window then restore it, everything will be back to normal more or less.

My guess is that it has something to do with the results window, like it was updating the UI at some point but never completes. And minimizing then restoring "cancels" that update returning control back to the UI thread.

I have some extensions defined to help with chaining expressions with common interfaces and operations.

public static class ChainableExtensions
{
    public static T With<T>(this T source, Action<T> action)
    {
        action(source);
        return source;
    }
    public static TResult Let<T, TResult>(this T source, Func<T, TResult> func)
    {
        return func(source);
    }

    #region IDictionary<TKey, TValue> extensions
    public static TDictionary AddChained<TKey, TValue, TDictionary>(this TDictionary dict, TKey key, TValue value) where TDictionary : IDictionary<TKey, TValue>
    {
        dict.Add(key, value);
        return dict;
    }
    ...
    #endregion

    #region IList<T> extensions
    public static TList InsertChained<T, TList>(this TList list, int index, T item) where TList : IList<T>
    {
        list.Insert(index, item);
        return list;
    }
    ...
    #endregion

    #region ISet<T> extensions
    public static TSet UnionWithChained<T, TSet>(this TSet set, IEnumerable<T> other) where TSet : ISet<T>
    {
        set.UnionWith(other);
        return set;
    }
    ...
    #endregion

    #region ICollection<T> extensions
    public static TCollection AddChained<T, TCollection>(this TCollection coll, T item) where TCollection : ICollection<T>
    {
        coll.Add(item);
        return coll;
    }
    ...
    #endregion
}

Autocomplete doesn't seem to take the constraints into account. All of the above methods are showing as options in autocomplete, even for types that do not satisfy the constraint. I feel like this should be fixed.

LinqPad Beta 7.1.4
.Net Runtime 6.0.1

Can you please try the 7.1.3 beta - this generates more diagnostic information.

After running, please post the latest entries in %localappdata%\linqpad\logs.linqpad7\log.txt

Thanks!

EF Core 6 doesn't support anything less than .NET 6.

You will need to use version 5 or earlier. Click "Add specific version to query" and choose 5.0.12.