Skip to content
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

What are the limitations running xaml in coreWF #194

Closed
pabloarthurrodger opened this issue Mar 1, 2022 · 7 comments
Closed

What are the limitations running xaml in coreWF #194

pabloarthurrodger opened this issue Mar 1, 2022 · 7 comments

Comments

@pabloarthurrodger
Copy link

As I read on your documentation, XAML produced by the designer (Visual Studio) can be run in CoreWF (with some limitations). I will like to know what are those limitations?

Thanks in Advance,

@dmetzgar
Copy link
Contributor

dmetzgar commented Mar 7, 2022

Just writing to let you know I saw your comment. I'd have to look into it a bit to have a detailed guide.

OTMH, the following are not supported:

  • Dynamic update, but very few people used that
  • Interop activity to run any WF3 activities
  • WCF activities like send and receive

@pabloarthurrodger
Copy link
Author

pabloarthurrodger commented Mar 8, 2022 via email

@pabloarthurrodger
Copy link
Author

pabloarthurrodger commented Mar 8, 2022 via email

@dmetzgar
Copy link
Contributor

dmetzgar commented Mar 8, 2022

Looking forward to seeing your implementation! It should be an interesting challenge.

Please find the source code of SqlWorkflowInstanceStore here: https://referencesource.microsoft.com/#System.Activities.DurableInstancing/System/Activities/DurableInstancing/SqlWorkflowInstanceStore.cs

Also have a look at the instance store documentation here: https://docs.microsoft.com/dotnet/framework/windows-workflow-foundation/instance-stores

@pabloarthurrodger
Copy link
Author

pabloarthurrodger commented Mar 16, 2022 via email

@dmetzgar
Copy link
Contributor

The code for TypedCompletedAsyncResult is in the JsonFileInstanceStore example. Rather than try to understand the older IAsyncResult pattern, I suggest using the Nito.AsyncEx library to convert to/from TPL (Task-based). Take a look at the interop documentation.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants