Support reading from string instead of file path
See original GitHub issueIt 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.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How to read variable contents instead of file path?
I have a Python function [1] which requires the file path pointing to the file it has to process as an argument. However,...
Read more >Mistakes I've Made Treating File Paths As Strings
Mistakes I've Made Treating File Paths As Strings · Don't Forget Windows · Paths Behave Differently to Strings · Always Use the Built-In...
Read more >Mistakes I've made treating file paths as strings
This post is about one of those things and if you're reading this, consider it me telling you. File paths look like strings....
Read more >bash - How to pass a string to a command that expects a file?
You can use the "fake" filename /dev/stdin which represents the standard input. So execute this: echo "$the_recipe" | cook /dev/stdin.
Read more >Path.Combine Method (System.IO)
This method is intended to concatenate individual strings into a single string that represents a file path. However, if an argument other than...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.
@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?