Joseph Musser

@romansp Thank you, that is much appreciated! Real quick, I have a question for you and @nunit/framework-team. We've been showing "Framework version" and calling it "CLR version." To me that's...

@ChrisMaddock Sure, I'm happy with that! Determining the runtime version would require a little research and so is outside the scope of this particular issue but we can start another....

> We should consider backwards-compat here Oh, I was thinking of them all as display strings but you're absolutely right. XML should stay `` while display labels can be `Framework...

@greentests We are about to address that, but for now, run `.\build.ps1 -t build` and the build in Visual Studio will start working. (It's not restoring NuGet packages correctly.)

Cool, thanks @stevenaw!

Will async event handlers wait for each other to finish running, and skip remaining handlers when any handler throws an exception, just like synchronous event handlers? This would require looping...

This proposal adds on #259, improving it in a way that would be [extremely helpful for me](https://github.com/dotnet/csharplang/issues/259#issuecomment-286110157). > Whatever we do here, I hope we don't block a future CLR...

@scottdorman #259 is explicitly asking for aliases internal to an assembly; my only need is for aliases that act externally.

@ufcpp Source generators don't help when what you're doing is using type aliases to rename an existing type without breaking binary compatibility of assemblies built against that type.

An example of where I would have used this recently is with the visitor pattern: ```c# class FooVisitor { public bool BarFlag { get; private set; } public void VisitNode(Node...