question

TZacks-2728 avatar image
0 Votes"
TZacks-2728 asked karenpayneoregon commented

C# & .Net core new features related articles


I am curios to know all the new features introduced in .net core & in c# regarding various version wise. i was searching few site to get few good article on this topic but not very lucky. so anyone can share few links of good articles which talk about C# & .Net core new features version wise and their advantages with example code to show usage.

in latest .net core is there any new data type of List<T> which works smarter than List<T> in terms of memory & speed of execution.

Thanks

dotnet-csharp
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I don't have any articles and since @cooldadtx memory/perf issues, perhaps you might like some simple code samples such as DateOnly, TimeOnly, PeriodicTimer and value converts for these types in EF Core check out my simple GitHub repository which requires the current SDK..
141911-figure1.png


1 Vote 1 ·
figure1.png (14.5 KiB)
PierreLucGiguere-5297 avatar image
0 Votes"
PierreLucGiguere-5297 answered

Hi Zack,

I personally start with the "What's new" section of the documentation

I find it easy to read. For example Web Forms is out ASP .Net Core Blazer is in.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

cooldadtx avatar image
1 Vote"
cooldadtx answered

in latest .net core is there any new data type of List<T> which works smarter than List<T> in terms of memory & speed of execution.

What memory/perf issues are you having with List<T>? It is one of the fastest dynamic array implementations available and therefore should be good enough. Of course if you're doing things that are inefficient then it won't perform well but that is on your code. Without any examples of perf/memory issues it is hard for us to tell you what to use better.

List<T> is backed by an array so for raw read (and generally) write speed it is probably the best. The runtime has gone through optimizations so you can expect a little perf improvements across the board but there hasn't been any new data structures added to beat List<T> as I'm not aware of anyone having issues. Perhaps you should use a different data structure if your having issues. .NET ships with others including hashsets, dictionaries and linked lists. They are all optimized for different scenarios so choose the one that is optimized for your use case.

If you believe there are perf issues with List<T> then submit a ticket in Github so the team can look at it but you'll need to provide some sample code that performs badly but shouldn't so they can test.



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.