Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. WPF
  4. Actual experience with WF

Actual experience with WF

Scheduled Pinned Locked Moved WPF
databasebusinesshelpquestion
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    Asher Barak
    wrote on last edited by
    #1

    Hi all, We develop classic business applications (relational DB, GUI etc.). We are considering implementing our business processes using WF. We consider WF as a means of simplifying development and making maintenance of complicated logic easier (Persisting, multiple async users, etc. are not relevant. The WF replaces a synchronous call to a static method). During the few weeks we have tested it we found out it does have some quirks and we also learned about the expected, totally different, ver 4 (though we cannot wait for it). We have not been able to find someone with actual working experience that can tell us weather working with this technology actually pays back. Can anyone help from their own experience? Thanks, Asher

    L 1 Reply Last reply
    0
    • A Asher Barak

      Hi all, We develop classic business applications (relational DB, GUI etc.). We are considering implementing our business processes using WF. We consider WF as a means of simplifying development and making maintenance of complicated logic easier (Persisting, multiple async users, etc. are not relevant. The WF replaces a synchronous call to a static method). During the few weeks we have tested it we found out it does have some quirks and we also learned about the expected, totally different, ver 4 (though we cannot wait for it). We have not been able to find someone with actual working experience that can tell us weather working with this technology actually pays back. Can anyone help from their own experience? Thanks, Asher

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Asher Barak wrote:

      Can anyone help

      I don't know that you are going to get very many responses but here's mine. About 2 years ago I had to implement several business processes in MFC. It was a nightmare and took a couple of months to get it worked out. My latest project is using WPF, WCF and WF. I decided to try WF for the processes that I had to do before and see if it would work for us or not. The first workflow took maybe 3 days to create and worked the way I expected the first time out. I have had to add things to it but the core has remained the same since. Worked out really great for me. The second workflow took less than 1 day to create the base. I had to shift to other priorites so it's not quite finished but I expect that I could finish it in a couple of hours. So the WF has worked out fine for me and I think that I am going to stick with it unless I discover some really compelling reason to switch. The big caveat here is that that I am not using any of the more advanced features of WF as yet. I am just doing some really basic stuff.

      Why is common sense not common? Never argue with an idiot. They will drag you down to their level where they are an expert. Sometimes it takes a lot of work to be lazy Individuality is fine, as long as we do it together - F. Burns Help humanity, join the CodeProject grid computing team here

      A 1 Reply Last reply
      0
      • L Lost User

        Asher Barak wrote:

        Can anyone help

        I don't know that you are going to get very many responses but here's mine. About 2 years ago I had to implement several business processes in MFC. It was a nightmare and took a couple of months to get it worked out. My latest project is using WPF, WCF and WF. I decided to try WF for the processes that I had to do before and see if it would work for us or not. The first workflow took maybe 3 days to create and worked the way I expected the first time out. I have had to add things to it but the core has remained the same since. Worked out really great for me. The second workflow took less than 1 day to create the base. I had to shift to other priorites so it's not quite finished but I expect that I could finish it in a couple of hours. So the WF has worked out fine for me and I think that I am going to stick with it unless I discover some really compelling reason to switch. The big caveat here is that that I am not using any of the more advanced features of WF as yet. I am just doing some really basic stuff.

        Why is common sense not common? Never argue with an idiot. They will drag you down to their level where they are an expert. Sometimes it takes a lot of work to be lazy Individuality is fine, as long as we do it together - F. Burns Help humanity, join the CodeProject grid computing team here

        A Offline
        A Offline
        Asher Barak
        wrote on last edited by
        #3

        Thanks, Asher

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups