CoreWCF
winforms
Our great sponsors
CoreWCF | winforms | |
---|---|---|
24 | 25 | |
1,596 | 4,212 | |
1.1% | 1.8% | |
7.7 | 9.3 | |
2 days ago | about 20 hours 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.
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.
winforms
-
Ask HN: Any way to write a simple desktop app anymore?
Windows Forms[0] is still alive and will never die, and very low overhead to start with, and works on new and shiny .NET 8.
If Linux or macOS, you can use AvaloniaUI[1] instead which is sufficiently advanced but assumes some prior knowledge.
[0] https://github.com/dotnet/winforms/blob/main/docs/getting-st...
[1] https://docs.avaloniaui.net/docs/get-started/
- A GitHub issue suggests the removal of the WebBrowser control in WinForms. If you think this is a bad idea, be sure to voice your disapproval on the issue!
-
Duda carrera: C#/.NET vs. Node/Express
Winforms: Licencia MIT.
-
We Got the Generics We Have (2022)
3. Therefore reified generics are not possible to implement in a backwards compatible way.
Ok, sure, but if you instead a new generic collection types and leave the old ones alone, you don’t have to worry about breaking existing compiled code.
This comment about C# suggests a lack of familiarity with the approach C# took:
> C# made the opposite choice — to update their VM, and invalidate their existing libraries and all the user code that dependend on it.
All of the pre-generic C# libraries continue to exist to this day (ArrayList, HashTable, and the non-generic IEnumerable). Applications that used them never stopped working. New code uses the generic collections (List and Dictionary).
Anyways, I think the costs that Java is currently paying for non-reified generics (reflection, performance, and type safety mentioned in the article) is not worth the backwards comparability with the 20 year old J2SE 1.4. The price C# pays for making a backwards incompatible generics (mostly some minor annoyance when designing a collection class implementing IEnumerable) is worth it at this point.
P.S. ok, I do admit that C# forking the collection library is still causing ongoing maintenance work 18 years later: https://github.com/dotnet/winforms/pull/8673
-
When A .NET Developer Learns Blazor
No, it is fully supported and in active development. https://github.com/dotnet/winforms
-
WPF Roadmap 2023
No, it's still under active development/maintenance. https://github.com/dotnet/winforms/graphs/contributors
-
Where are these images stored?
The image is kept in-memory— https://github.com/dotnet/winforms/blob/main/src/System.Windows.Forms/src/System/Windows/Forms/PictureBox.cs
-
Does anyone know how to make a UITypeEditor for Winforms that works in .NET 6?
Appears that this has been broken for a while. Seems it has something to do with the new designers being run out of process.
-
Why is Microsoft's C# not taught in most universities and Java is instead?
Also, the runtime that C# runs on, is also completely open source as well (https://github.com/dotnet/runtime); ASP.NET which is used to create web apps in C# is open as well (https://github.com/dotnet/aspnetcore). WinForms/WPF, used to make desktop apps in C# is also open source (https://github.com/dotnet/wpf, https://github.com/dotnet/winforms). All of the source code for these are on the dotnet Github page: https://github.com/dotnet and most are all MIT-licensed.
-
Announcing .NET 7 Preview 5
You'll likely have to open an issue against https://github.com/dotnet/winforms. If you've already opened an issue here, then feel free to link and I might be able to provide suggestions on how to improve the triage process.
What are some alternatives?
SoapCore - SOAP extension for ASP.NET Core
Avalonia - Develop Desktop, Embedded, Mobile and WebAssembly apps with C# and XAML. The most popular .NET UI client technology
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
Xamarin.Forms - Xamarin.Forms Official Home
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
Visual Studio Code - Visual Studio Code
wcf - This repo contains the client-oriented WCF libraries that enable applications built on .NET Core to communicate with WCF services.
Unity-WinForms - A Windows Forms port for Unity3d
zeebe-dapr-example - An example that allows to orchestrate Dapr microservices with the Zeebe process engine.
Windows UI Library - Windows UI Library: the latest Windows 10 native controls and Fluent styles for your applications