Ivan Josipovic

+1

I have updated the readme with a new approach on how to set the instrumentation key. See, https://github.com/IvanJosipovic/BlazorApplicationInsights#set-instrumentation-key-programmatically

> Also, I suppose this specific feature request is for a programmatic API to set the connection string. Right now there's only SetInstrumentationKey. I looked into this briefly in the...

> I take it that `SetConnectionString` does not 100% work yet? Based on my attempts to get it to work and getting an error that it could not find `blazorApplicationInsights.setConnectionString`....

Not that I'm aware of. I keep it on but use a Dev App Insights instance so that alerts don't trigger. Additionally, you could use an adblocker.

> I think the intention is to keep BlazorTable at .NET Standard 2.1 and referencing Blazor 3.x libraries for the moment so I don't think this PR can be accepted....

@conficient, thank you for your help. Please familiarize yourself with https://www.conventionalcommits.org/en/v1.0.0/ This will enable automatic package versioning, and prevent the PR bot from blocking a PR. Here are some example...

Hey, Can you give this a try? https://bunit.egilhansen.com/api/Bunit.Extensions.LoggerHelperExtensions.html If you get stuck, let me know where the code is and I can have a look. Thank you!

I think the CSV export can be implemented very easily. See the following Issue which shows how to retrieve the Filtered Items, https://github.com/IvanJosipovic/BlazorTable/issues/118 I'll think about If I would like...

Hi all, I have added all the requested features to the list. Please make any suggestions in a new issue so that we can have a easier discussion.