CoreCLR
CoreWCF
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.
CoreCLR
-
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)
- How are stack machines optimized?
-
Best .net/c# resources for senior engineer
Sort of, some topic are not relevant anymore, consider this - https://github.com/dotnet/coreclr/tree/master/Documentation/botr
-
Is there a C# under the hood tutorial?
Fairly advanced stuff but the Book Of The Runtime (BOTR) it's a invaluable resource
-
In depth learning of C#?
After that you can check out the The Book of the Runtime, which is the CoreCLR version of the previous book.
-
.NET 6 is now in Ubuntu 22.04
Technically the restrictions already exist, just as a part of the development experience.
- .NET Hot Reload is only implemented on Windows. It requires support in the .NET runtime, which is technically possible to implement, but the team has not gotten around to implementing it for years. This doesn't have to do with the issue around MS removing the "dotnet watch" command, it's for the "Edit and Continue" feature in IDEs.[1][2]
- MS was considering deprecating Omnisharp, the open-source language server that implements C# support for VS Code, and replacing it with a closed-source version. Since the announcement, commits to omnisharp-vscode have dropped off significantly. The lack of Omnisharp would mean there would be no real open-source C# development environment for Linux anymore, since MonoDevelop was abandoned a few years ago. [3]
[1] https://youtrack.jetbrains.com/issue/RIDER-31366/EditContinu...
[2] https://github.com/dotnet/coreclr/issues/23685
[3] https://github.com/omnisharp/omnisharp-vscode/issues/5276
-
what a .NET specialist should know
The next step is to realize everything you think you know about .NET is just an abstraction. Next step is to learn about what is going on behind all that syntax sugar and facades. 1st step might be https://github.com/dotnet/coreclr/tree/master/Documentation/botr then go down the rabbit hole and have fun
- Trouble with random numbers
-
Is CLR via C# still good?
Book of the Runtime
-
Understanding dotnet
As for the books, back in the days I really enjoyed reading “CLR via C#" by Jeffrey Richter which helped a lot to understand what is under the hood. Other from that, try The Book of the Runtime
CoreWCF
-
How do I approach migrating from .net framework WCF to .net core web api
CoreWCF might be of some use.
-
Having a heck of a time getting WCF web.config working correctly.
You can open a discussion in the CoreWCF repo:
-
Why WCF? Am I wrong for hating it so much?
In the later versions you could avoid almost all the XML mess by configuring all of the settings in code. The experience is pretty close to gRPC imo, one plus point is you don't need to learn how to write proto classes. Though you could use protobuf-net for a similar experience. I'm kinda hopeful with CoreWCF, they aim to support more transports (including event gRPC) in the future along with queues other than MSMQ and slowly evolve from being too SOAP specific. There's a lot of potential still for WCF to be a transport agnostic framework that ecompass a lot of transports.
- OpenAPI vs SOAP and WSDL
-
.NET 7 is Available Today
On our end, it's WCF for some servers that haven't been upgraded over. Though it seems we have a path forward for that now with CoreWCF that we're working towards.
-
Bring WCF apps to the latest .NET with CoreWCF and Upgrade Assistant
There's ongoing work on adding generic queue support. The first two concrete implementations should be MSMQ and RabbitMq from what I recall, though MSMQ will be windows only. But the nice thing about the work is it also opens up other types of message queues for WCF (e.g. Azure Service Bus, RabbitMq, Amazon SQS etc...).
- .NET 6 is now in Ubuntu 22.04
-
CoreWCF 1.1.0 release and project templates
It's seems there's already design work started for a generic queue concept here. I'm pretty interested to see how it goes as well as that'll be a big part for CoreWcf to move forward as a viable choice for greenfield projects and not just a way to migrate existing Wcf projects to Core.
-
Questions about OWIN and WCF from a high level.
The ongoing .net core port called CoreWcf plans to realize that goal as a future feature on it's roadmap. Where there's plans on adding new transports that didn't exist on .net framework wcf like Grpc, Azure Service bus, Amazon SQS, rabbitmq etc...
-
CoreWCF v1.0.0 released and comes with official support from Microsoft
If you hit any difficulties or have any problems, feel free to jump on the gitter channel. Details for that are in the repo contributing guide.
What are some alternatives?
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
SoapCore - SOAP extension for ASP.NET Core
sdk - Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
FrameworkBenchmarks - Source for the TechEmpower Framework Benchmarks project
referencesource - Source from the Microsoft .NET Reference Source that represent a subset of the .NET Framework
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
AspNetCore-Developer-Roadmap - Roadmap to becoming an ASP.NET Core developer in 2024
wcf - This repo contains the client-oriented WCF libraries that enable applications built on .NET Core to communicate with WCF services.
Windows UI Library - Windows UI Library: the latest Windows 10 native controls and Fluent styles for your applications
zeebe-dapr-example - An example that allows to orchestrate Dapr microservices with the Zeebe process engine.