BOborissk·May 3, 2023
Wonder how does it compare to https://github.com/UiPath/CoreWF
In Temporal .NET – Deterministic Workflow Authoring in .NETUiPath
CoreWF
C#2023–2023
UiPath / CoreWF
CoreWF
WF runtime ported to work on .NET 6
2Distinct people
2Mentions
0Explicit recommenders
1.2KGitHub stars
What to know before exploring
What it is
WF runtime ported to work on .NET 6
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by week2 dated mentions
Observed mentions: 2023-03-22 00:52:39 UTC to 2023-05-03 17:00:53 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Mar 20 | 2023-03-20 00:00:00 UTC | 2023-03-27 00:00:00 UTC | 1 | 0 | 1 |
| Mar 27 | 2023-03-27 00:00:00 UTC | 2023-04-03 00:00:00 UTC | 0 | 0 | 0 |
| Apr 3 | 2023-04-03 00:00:00 UTC | 2023-04-10 00:00:00 UTC | 0 | 0 | 0 |
| Apr 10 | 2023-04-10 00:00:00 UTC | 2023-04-17 00:00:00 UTC | 0 | 0 | 0 |
| Apr 17 | 2023-04-17 00:00:00 UTC | 2023-04-24 00:00:00 UTC | 0 | 0 | 0 |
| Apr 24 | 2023-04-24 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 1 | 2023-05-01 00:00:00 UTC | 2023-05-08 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
2 sources> The writing was on the wall a long, long time ago!
The vast majority of ASP.NET Web Apps could not have migrated to .NET Core 1.0, it was missing too many features. It was missing types like 'securestring', and had zero support for Workflow Foundation, Windows Communication Foundation, etc...
At the time, .NET Core was also advertised as "an alternative platform for Linux apps", not as a direct replacement for .NET Framework.
It was only in .NET 5 that Microsoft changes their tune and started calling Core the "replacement". At the time, something like half of complex enterprise apps might be able to migrate across, but they would have encountered a long list of breaking issues with a note saying "we might fix that in an upcoming major release". That's after a partial rewrite.
You can't go to a business that has a web app that's "not bro
Read the rest
ken" and suggest migrating it to a definitely broken platform that's very much still playing "catch up".
Support is improving in .NET 7, and the upcoming .NET 8, but it's definitely not 100% and pretending that it's the "end users' fault" for not jumping onto an incomplete and buggy platform is not helpful.
I'll list some random GitHub issues for you to perouse. For large enterprise apps, many of these are showstoppers for incremental or seamless migrations. The workaround is always "rewrite everything from scratch using wildly different technologies that aren't direct replacements."
IIS app pool recycle throws 503 errors
https://github.com/dotnet/aspnetcore/issues/41340
OData core libraries now support OData v4
https://devblogs.microsoft.com/odata/announcement-odata-core-libraries-now-support…
(.NET Framework is v1-v3, and Core is 4.0+, a breaking change!)
Workflow Foundation didn't start getting migrated until .NET 6, and not by Microsoft!
https://github.com/UiPath/corewf
dotnet-svcutil ignores most of the settings
https://github.com/dotnet/wcf/issues/4887
dotnet-svcutil silently failing to deserialize responses
https://github.com/dotnet/wcf/issues/4163
Reuse of Types not working with WCF dotnet-svcutil tool for .NET Core
https://github.com/dotnet/wcf/issues/4277
Visual Studio 16.8 breaks SvcUtil build targets
https://github.com/dotnet/wcf/issues/4431