Build productive Python web applications with Visual Studio Code, Azure and Azure DevOps

Several new language features are coming to C# in the next release, included in Visual Studio 2019. Mads Torgersen will give us a quick look at how to avoid null reference exceptions with nullable reference types, how to consume and produce asynchronous streams, and much more.
Twitter: @MadsTorgersen
Learn more about C# 8.0: https://aka.ms/csharp8
absolute *
How to set project level nullable context?
Cool thanks! :D
What is in store for VB.net?
in .csproj
file:
<PropertyGroup>
...
<NullableReferenceTypes>true</NullableReferenceTypes>
<LangVersion>8.0</LangVersion>
</PropertyGroup>
What is "default" for non-nullable string?
string str = default; // converting null literal or possible null value to non- / // nullable type
This gives the same warning as replacing "default" with null;
@ArneG: Kathleen posted about VB a couple of weeks ago:
https://blogs.msdn.microsoft.com/vbteam/2018/11/12/visual-basic-in-net-core-3-0/
@GodwinK: Nullable reference types do not change runtime semantics of the language - all they do is add warnings. So default(string) remains null, but gets a warning.
For a kind of project i am doing i am generating a schema from functions header/prototype. Currently i have two generic classes NonNull<T> and Nullable<T>. My version of Nullable is different to C#'s.
void MyFunc(NonNull<string> a, Nullable<string> b)
{
}
Then i generate some schema using Reflection in run-time.
I tried the same thing with C# 8.0 but running Console.WriteLine(typeof(string?).Name) prints String.
Is there any solution i can know if the function argument is nullable or not ?
Can the IAsyncEnumerable already be tested in Visual Studop 2019 prview 1 with .NET Core SDK 3.0.100-preview-009812?
While consuming seems to be no problem using yield return in an Method returning IAsyncEnumerable can't compile. With an strange error
C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview\MSBuild\15.0\Bin\Roslyn\Microsoft.CSharp.Core.targets(52,5): error MSB6006: "csc.exe" wurde mit dem Code -2146232797 beendet.
LokiMidgard, this is what happens when you have German developers in your team :-))))
This is really good. I've been playing with it for a bit now; huge improvements and greatly appreciated.
Glad to see pattern matching make it into the language, it will help a lot.
Great, thanks for this. It will make my work so much easier.
I am stuck with LabVIEW and it is great but really sad at other times.
Fortunately it really works well with .NET platform and I can just do my work in C#.
I just need some wrappers for complex numbers operations between those two.
Slices are really great, used to do prototyping in Python but C# wins this one now.