ShadowMarker789

I had just recently upgraded my game project to .Net 6 since I wanted to use certain libraries that only work in .Net 6 - turns out the upgrade caused...

As it happens if you ignore those exceptions thrown everything continues to work but while it's busy throwing an exception for every assembly loaded we're eating a lot of overhead...

Did some testing by cloning and modifying. Pull request created: [Bugfix Pull Request](https://github.com/neolithos/neolua/pull/143)

I don't suppose the feasibility of implementing the full set of features available in Microsoft.SqlServer.DacFx.x64 Nuget which is .Net Framework into .Net Standard, Core, 5, or 6 has changed since...

I have a setup in place where there's one core tag that's always monitored, and the "other" tags are monitored only if that one came clean on last read. But...

I had to redact out a bunch of stuff to comply with NDA compliance which is annoying. I am considering that perhaps I should be doing a Parallel.ForEach on the...

When each Tag-association is created, it spawns and runs the task, so we have a long-running task per tag. I'll see if I can refactor my code to a Parallel-Foreach...

I am having better performance with Parallel.For. ` Parallel.For(0, lastTagCount, po, async (i) => { await tagList[i].PollAsync(); }); ` Where po is ParallelOptions setting a MaxDegreeOfParallelism of ProcessorCount / 2...

For any TryXYZ methods, my personal preference would be to have these methods return the LibPlcTag.Status enum if they are synchronous methods, else returning Task This way you can easily...

> Is there a reason you would want to use the status to differentiate between the failure modes? The TryXYZ methods I've seen have all returned a boolean for success/failure....