The .NET Compiler Platform ("Roslyn") provides open-source C# and Visual Basic compilers with rich code analysis APIs.
in new csproj
Hey guys, I have the following test code for me to understand stream behavior:
[Fact]
public async Task TestAsync()
{
using var cts = new CancellationTokenSource(10_000);
// Memory stream simulating network.
using var stream = new MemoryStream();
// Server: Read the AUTHENTICATE command from client.
using var streamReader = new StreamReader(stream, Encoding.ASCII, leaveOpen: true);
using var streamWriter = new StreamWriter(stream, Encoding.ASCII, leaveOpen: true);
streamWriter.Write('X');
streamWriter.Flush();
string v = streamReader.ReadToEnd();
Assert.Equal("X", v);
}Apparently, this seems to be fundamentally wrong. I was hoping to use streams to simulate data flowing through TcpClient. But it looks like I can't read & write to the same stream at the same time.
So I basically don't know whether
Stream is supposed to be bi-directional or uni-directional data structure.
Mostly, it's used as uni-directional - i.e. reading files, reading from network stream.
because you're wrapping the same stream, writing to it advances the cursor of where it is, so the
Read right after thinks that it's at the end of the stream
if you want to read from that stream you need to rewind it before reading
God, thanks!
and since there's been an effort to plumb Pipes (pun half-intended) through the networking stack, that's probably a better option to look at
Thanks guys!
If you do want to use Stream as your abstraction, you probably want to implement Stream yourself, rather than using MemoryStream: MemoryStream doesn't have a concept of separate read and write queues, it's all just one big array with a single position, which is used for both reading and writing
I see, now I understand! I'm reading https://docs.microsoft.com/en-us/dotnet/standard/io/pipelines now
Impressed by the intro :)
Pipelines don't even bother
OK. Now I've implemented everything I can find about conditional await in the compiler layer. The branch is at https://github.com/huoyaoyuan/roslyn/tree/features/conditional-await . Could you consider this a candidate of community contribution?
i've championed this and will try to get this reviewed in our next triage meeting
37 replies
I think all the source code for the SDK is at https://github.com/dotnet/sdk
You'll be mimicking specialized subsets of its behavior, like packing into a single .exe
I would be very surprised if there are any guides on how to replicate this without the SDK, but there might be a blog post on the principles of what it does or on how the SDK does it.
Otherwise all you have is design docs and SDK source code.
If you don't enjoy doing all the investigation and footwork yourself, you will not enjoy this route
What you're after is not to perfectly mimic the SDK of course, from what I hear. All you need to know are the principles of how to emit a native windows .exe that extracts files to a temp folder or maps them into memory right out of the .exe file.
E.g. how to pick a temp folder name to use as a cache, how to safely allow multiple instances to start concurrently, etc
Oh, there's another possibility. Instead of using the SDK or implementing this yourself, there might be an existing tool that does all the packing for you with a license that allows you to redistribute it inside your app.
Laziness is a virtue IMO
I am trying to use SymbolFinder.FindReferencesAsync inside an analyzer, I need access to the Solution object. Is there a way around that? I remember there was a reason why we don't have access to the solution in an analyzer, or do we? I can't seem to remember what is the reason though.