-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XAML/WCF activities current limitations update? #222
Comments
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. |
As this is generic and should be valid for all projects, do you know if a mapping (old namespace => new namespace) already exist somewhere ? |
@dmetzgar - Couple quick questions related to the listed limitations here: #194
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.
The text was updated successfully, but these errors were encountered: