Karl Waclawek
Karl Waclawek
FYI - I just forked FlatBuffers and converted the C# project to the new .NET core format, adding support for netstandard 1.1. This is published as a Nuget package: https://www.nuget.org/packages/KdSoft.FlatBuffers/...
I updated my fork to v1.12 and published the C# project as a Nuget package, supporting netstandard 1.1 and 2.0: https://www.nuget.org/packages/KdSoft.FlatBuffers/ Note: I changed the C# namespace from FlatBuffers to...
Should be in the package under Tools. On Sun., Mar. 14, 2021, 11:57 a.m. Kyle Tse, ***@***.***> wrote: > I updated my fork to v1.12 and published the C# project...
This might be a documentation issue, because when loaded inside of an ES6 module, the "this" inside of the function assigned to var i18n is only defined when usinge "new",...
So, is using [Google.Api.CommonProtos](https://www.nuget.org/packages/Google.Api.CommonProtos/) now the canonical way of using the rich error model?
> I am very interested understanding why this feature is not part of the core. Is not that popular/needed among GRPC users? How are devs dealing with errors and validation...
This issue is probably dead by now, but I'd just like to leave a comment to state that a live CtfTraceEventSource would still be useful. The recommended approach with EventPipe...
Still seems to be an issue with Microsoft.Diagnostics.Tracing.TraceEvent 2.0.48
Seems this issue has fallen off the radar. Is there a workaround?
I guess one could add a configuration item like "UseLegacyTypeHandling" which is turned on by default to maintain backwards compatibility.