TodoApi
.NET Runtime
TodoApi | .NET Runtime | |
---|---|---|
10 | 612 | |
2,670 | 14,231 | |
- | 2.2% | |
3.7 | 10.0 | |
about 2 months ago | 5 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
TodoApi
-
ASP.NET Core beginner struggling to find open-source projects to learn or build
Shameless plug https://github.com/davidfowl/TodoApi
-
Blazor Authentication - Understanding OpenIDConnect vs IdentityServer?
This is a fairly common scenario (externalizing the authentication piece but still wanting app-local storage of some user information) that isn't well documented (we're working on that). You might try taking a look at this app by u/davidfowl that supports what you're asking about: https://github.com/davidfowl/todoapi
-
Please guide me on how to start with Authentication vs Authorization in a .net blazor webassembly.
Good news: David Fowler has a full showcase repository TodoApi
- Creating Angular and C# application
-
Azure B2C or ASP.NET Core Identity for API that services SPA and Mobile app
ASP.NET Core Identity.However, most examples use Identity with the MVC/Blazor. I need to support both a SPA and a mobile app and I am not sure if that is the recommended approach here.(Perhaps I should use the backend for frontend approach like David Fowler showcases in https://github.com/davidfowl/TodoApi ?)
- any good (asp.net core) repositories for studying ?
-
MinimalAPI Github repositories
Throwing mine in the ring https://github.com/davidfowl/TodoApi/
-
Easiest/Standard way to implement a simple HTTP REST API?
Example at https://github.com/davidfowl/CommunityStandUpMinimalAPI/blob/main/TodoApi/Program.cs
-
Ask HN: Examples of Top C# Code?
A basic example looks like: https://github.com/davidfowl/CommunityStandUpMinimalAPI/blob...
Some more documentation on integration tests: https://learn.microsoft.com/en-us/aspnet/core/test/integrati...
-
I need a C# crash course for experienced developers
Pre .NET 6, there's a Startup.cs file that is used to set these up. .NET 6+ just puts them in Program.cs by default, but you can still use a Startup.cs if you'd prefer. Example of the newer template in Program.cs is here
.NET Runtime
-
The search for easier safe systems programming
.NET has explicit tailcalls - they are heavily used by and were made for F#.
https://learn.microsoft.com/en-us/dotnet/api/system.reflecti...
https://github.com/dotnet/runtime/blob/main/docs/design/feat...
-
Arena-Based Parsers
The description indicates it is not production ready, and is archived at the same time.
If you pull all stops in each respective language, C# will always end up winning at parsing text as it offers C structs, pointers, zero-cost interop, Rust-style struct generics, cross-platform SIMD API and simply has better compiler. You can win back some performance in Go by writing hot parts in Go's ASM dialect at much greater effort for a specific platform.
For example, Go has to resort to this https://github.com/golang/go/blob/4ed358b57efdad9ed710be7f4f... in order to efficiently scan memory, while in C# you write the following once and it compiles to all supported ISAs with their respective SIMD instructions for a given vector width: https://github.com/dotnet/runtime/blob/56e67a7aacb8a644cc6b8... (there is a lot of code because C# covers much wider range of scenarios and does not accept sacrificing performance in odd lengths and edge cases, which Go does).
Another example is computing CRC32: you have to write ASM for Go https://github.com/golang/go/blob/4ed358b57efdad9ed710be7f4f..., in C# you simply write standard vectorized routine once https://github.com/dotnet/runtime/blob/56e67a7aacb8a644cc6b8... (its codegen is competitive with hand-intrinsified C++ code).
There is a lot more of this. Performance and low-level primitives to achieve it have been an area of focus of .NET for a long time, so it is disheartening to see one tenth of effort in Go to receive so much spotlight.
-
Airline keeps mistaking 101-year-old woman for baby
It's an interesting "time is a circle" problem given that a century only has 100 years and then we loop around again. 2-digit years is convenient for people in many situations but they are very lossy, and horrible for machines.
It reminds me of this breaking change to .Net from last year.[1][2] Maybe AA just needs to update .Net which would pad them out until the 2050's when someone born in the 1950s would be having...exactly the same problem in the article. (It is configurable now so you could just keep pushing it each decade, until it wraps again).
Or they could use 4-digit years.
[1] https://github.com/dotnet/runtime/issues/75148
-
The software industry rapidly convergng on 3 languages: Go, Rust, and JavaScript
These can also be passed as arguments to `dotnet publish` if necessary.
Reference:
- https://learn.microsoft.com/en-us/dotnet/core/deploying/nati...
- https://github.com/dotnet/runtime/blob/main/src/coreclr/nati...
- https://github.com/dotnet/runtime/blob/5b4e770daa190ce69f402... (full list of recognized keys for IlcInstructionSet)
-
The Performance Impact of C++'s `final` Keyword
Yes, that is true. I'm not sure about JVM implementation details but the reason the comment says "virtual and interface" calls is to outline the difference. Virtual calls in .NET are sufficiently close[0] to virtual calls in C++. Interface calls, however, are coded differently[1].
Also you are correct - virtual calls are not terribly expensive, but they encroach on ever limited* CPU resources like indirect jump and load predictors and, as noted in parent comments, block inlining, which is highly undesirable for small and frequently called methods, particularly when they are in a loop.
* through great effort of our industry to take back whatever performance wins each generation brings with even more abstractions that fail to improve our productivity
[0] https://github.com/dotnet/coreclr/blob/4895a06c/src/vm/amd64...
[1] https://github.com/dotnet/runtime/blob/main/docs/design/core... (mind you, the text was initially written 18 ago, wow)
-
Java 23: The New Features Are Officially Announced
If you care about portable SIMD and performance, you may want to save yourself trouble and skip to C# instead, it also has an extensive guide to using it: https://github.com/dotnet/runtime/blob/69110bfdcf5590db1d32c...
CoreLib and many new libraries are using it heavily to match performance of manually intensified C++ code.
-
Locally test and validate your Renovate configuration files
DEBUG: packageFiles with updates (repository=local) "config": { "nuget": [ { "deps": [ { "datasource": "nuget", "depType": "nuget", "depName": "Microsoft.Extensions.Hosting", "currentValue": "7.0.0", "updates": [ { "bucket": "non-major", "newVersion": "7.0.1", "newValue": "7.0.1", "releaseTimestamp": "2023-02-14T13:21:52.713Z", "newMajor": 7, "newMinor": 0, "updateType": "patch", "branchName": "renovate/dotnet-monorepo" }, { "bucket": "major", "newVersion": "8.0.0", "newValue": "8.0.0", "releaseTimestamp": "2023-11-14T13:23:17.653Z", "newMajor": 8, "newMinor": 0, "updateType": "major", "branchName": "renovate/major-dotnet-monorepo" } ], "packageName": "Microsoft.Extensions.Hosting", "versioning": "nuget", "warnings": [], "sourceUrl": "https://github.com/dotnet/runtime", "registryUrl": "https://api.nuget.org/v3/index.json", "homepage": "https://dot.net/", "currentVersion": "7.0.0", "isSingleVersion": true, "fixedVersion": "7.0.0" } ], "packageFile": "RenovateDemo.csproj" } ] }
-
Chrome Feature: ZSTD Content-Encoding
https://github.com/dotnet/runtime/issues/59591
Support zstd Content-Encoding:
- Writing x86 SIMD using x86inc.asm (2017)
-
Why choose async/await over threads?
We might not be that far away already. There is this issue[1] on Github, where Microsoft and the community discuss some significant changes.
There is still a lot of questions unanswered, but initial tests look promising.
Ref: https://github.com/dotnet/runtime/issues/94620
What are some alternatives?
FastEndpoints - A light-weight REST API development framework for ASP.NET 6 and newer.
Ryujinx - Experimental Nintendo Switch Emulator written in C#
Stripe.Net - Stripe.net is a sync/async .NET 4.6.1+ client, and a portable class library for stripe.com.
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
FakeItEasy - The easy mocking library for .NET
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
NodaTime - A better date and time API for .NET
WASI - WebAssembly System Interface
practical-aspnetcore - Practical samples of ASP.NET Core 8.0, 7.0, 6.0, 5.0, 3.1, 2.2, and 2.1,projects you can use. Readme contains explanations on all projects.
CoreCLR - CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.
Shouldly - Should testing for .NET—the way assertions should be!
vgpu_unlock - Unlock vGPU functionality for consumer grade GPUs.