Skip to main content

Workflows using CoreWF in .net core

Workflow Foundation is a great tool when designing workflows for .net. Unfortunately, just like WCF, that technology is not going to be ported to .net core. However, a company named UI Path (https://www.uipath.com/)  that heavily relies on Windows Workflow Foundation, has started an unofficial port to .net (https://github.com/UiPath-Open/corewf).

In order to see how compatible would be the the new port with the current Windows Workflow for simple workflows, I created a playground project at  https://github.com/jptarqu/WorkflowForCorePlayground . The Visual Studio solution contains two projects:


  1. WorkflowForCorePlayground : a VB.net Windows Workflow project created using the VS template for .net 4.8. 
  2. CoreWfSample : a .net core console app that runs a cleaned version of the same xaml that project #1 has.
The idea is to explore the possibility of still having business users design the workflow using the regular .net framework 4.8 beautiful and easy-to-use designer, while still been able to run the workflow in .net, in for example an Azure Server-less Function. Obviously,  not all Workflow Activities would work with .net core, but hopefully simple workflows and flow charts encapsulating business rules can be used.

In order to use the CoreWF you must install the nuget in your project. But the nuget does not seem to be in Nuget.org, so you have to add the following url to yur nuget sources in Visual Studio:

https://www.myget.org/F/uipath-dev/api/v3/index.json

The .net core project works without needing to modfiy the xaml. I was able to copy and paste the xaml code from the xaml generated by the visual studio designer into the xaml file in my .net core.

My next experiment is to try creating an Azure Function that runs the xaml workflow.


Comments

Popular posts from this blog

Alert if file missing using Powershell

The following Powershell script can be used to send an email alert when a file is missing from a folder or it is the same file from a previous check: $path_mask = "yourfile_*.txt" $previous_file_store = "lastfileread.txt" $script_name = "File Check" ###### Functions ########## Function EMailLog($subject, $message) {    $emailTo = "juanito@yourserver.com"    $emailFrom = "alert@yourserver.com"    $smtpserver="smtp.yourserver.com"       $smtp=new-object Net.Mail.SmtpClient($smtpServer)    $smtp.Send($emailFrom, $emailTo, $subject, $message) } Try {    #get files that match the mask    $curr_file = dir $path_mask |  select name    if ($curr_file.count -gt 0)    {        #file found        #check if the file is different from the previous file read        $previous_file = Get-Content $previous_file_store        $curr_file_name = $curr_file.Item(0).Name        if ($

Power Automate: SFTP action "Test connection failed"

When I added an SFTP create file action to my Power Automate flow ( https://flow.microsoft.com ) , I got the following error in the action step, within the designer: "Test connection failed" To troubleshoot the Power Automate connection, I had to: go the Power Automate portal then "Data"->"Connections"  the sftp connection was there, I clicked on the ellipsis, and entered the connection info It turns out, that screen provides more details about the connection error. In my case, it was complaining that "SSH host key finger-print xxx format is not supported. It must be in 'MD5' format". I had provided the sha fingerprint that WinScp shows. Instead, I needed to use the MD5 version of the fingerprint. To get that, I had to run in command line (I was in a folder that had openssh in it): ssh -o FingerprintHash=md5 mysftpsite.com To get the fingerprint in MD5 format. I took the string (without the "MD5:" part of the string) and put

How to use Windows SSO with OpenXava

One of the nice things about the .NET web environment is the dead easy way to implement Single Sign On in your web apps through Active Directory authentication. In the Java world there are multiple alternatives to use Windows’ Single Sign On with Java based web apps. One of those alternatives is Waffle . Waffle allows your Java web app to authenticate against Active Directory groups (and users). The only caveat is that your web server needs to be running in Windows, which kind of makes sense. In this article, you will learn the steps required to have your OpenXava web application use Waffle to authenticate your Windows users. The first step is to download Waffle from their site and then copy the JAR files outlined in https://github.com/dblock/waffle/blob/master/Docs/tomcat/TomcatSingleSignOnValve.md to the OpenXava’s tomcat server. In your OpenXava project, create servlets.xml in the Web-inf, containing the following: <!-- the role name (the domain gorup) must be e