-
-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support reading from string instead of file path #183
Comments
string is not binary (it has encoding), but I can certainly imagine Stream and byte[]. Would that work? |
This would definitely help. Would be great to have this possibility for reading |
How's this change? Would you please build it yourself and try it out? If it works fine, I can publish the next update. |
@KirillOsenkov Thanks! Works fine for my use case |
Thanks! Published a new release here: |
@KirillOsenkov Do you have any plans to update the NuGet package to a recent version, or is there a specific reason why it is still at 1.1.224? |
Microsoft has introduced additional security requirements to publish NuGet packages under Microsoft.*. There's a few hoops I'd need to jump through, like signing, internal security groups, etc. I don't have time nowadays for that, but I am aware that the NuGet packages are behind and want to fix this as soon as I have time. I apologize for the inconvenience. I'll either find time to set up upload infrastructure again or move to a non-Microsoft package id. |
It would be nice if there would be an overload of
BinaryLogReplayEventSource.ReadRecords
which accepts a string instead of a file path, for cases where the log file content is already available in memory.The text was updated successfully, but these errors were encountered: