XAML/WCF activities current limitations update?

[briannoyes]

@dmetzgar - Couple quick questions related to the listed limitations here: #194

• When you say WCF activities like Send and Receive don't work, is that only in the context using those activities from xaml, or does that mean WCF calls in/out don't work on top of CoreWF as a whole?
• Since durable instancing and workflow lifecycle are often driven by workflow services calls, is there a replacement for WCF send/recieve - i.e. REST endpoint and HttpClient calls out?
• Are there other activities or expressions or runtime limitations in XAML workflow definitions?

A little hard to tell the answers on these since there is mostly out of date info out there other than the evolution of the code.

[dmetzgar]

CoreWF, in it's current version, is meant for .NET 6. .NET 6 doesn't have WCF. There is a CoreWCF project out there but it is not integrated with CoreWF. HTTP/REST calls are not implemented in a generic activity in the CoreWF library.

When it comes to limits with XAML, the Interop activity for using WF3 inside WF4 is not there. Dynamic Update is not implemented. And the biggest difference when switching from .NET Framework WF to CoreWF is that some of the assemblies change. For instance, in Framework you have a lot of types defined in mscorlib but in .NET Core/5+ these would be in different assemblies like System.Runtime. This can be fixed by modifying the assembly names in the XML namespace declarations.

[Fabsky]

This can be fixed by modifying the assembly names in the XML namespace declarations.

As this is generic and should be valid for all projects, do you know if a mapping (old namespace => new namespace) already exist somewhere ?