Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Include `System.Threading.Tasks` to the standard namespaces
See original GitHub issueIt’s not convenient to create samples that use modern TAP based async work because the System.Threading.Tasks namespace is not included by default. That could lead people to use older APIs instead of the async and await based protocol.
I had a conversation on email about this with @TheRealPiotrP that this change would make the default interactive experience different than the local experience for Visual Studio or dotnet CLI users. Should this concept be expanded to update the default list of imported namespaces in the C# templates for Visual Studio and dotnet new. /cc @KathleenDollard @Pilchie
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@BillWagner It appears to work perfectly on the link that you gave me.
I get autocomplete and everything.
@TyOverby This works perfectly for the try.dot.net experience.
I’d like to have similar functionality for the docs.microsoft.com quickstart experience.
/cc @TheRealPiotrP @LadyNaggaga Is there a different location for this feature request?