Condividi tramite

WF 4.0 -- Designer Type Visibility

  • Articolo

One of the exercises I'm going through now is scrubbing our API and taking a hard look at types marked as public and trying to decide "does it really need to be public."  While on first blush, you can

What I'd love to get from folks are answers to the following questions:

  • Were there designer types in 3.0/3.5 that were not public that caused you problems?
    • If so, why?  What and how did you want to use that type?
  • Were there scenarios where you found our decisions on type visibility odd, inconsistent or painful?  Let me know what those were.

 

Looking forward to your thoughts!

Comments

  • Anonymous
    February 25, 2009
  1. StateMachineDesigner. I want to override some methods and not recreate all. I had to use FreeformActivityDesigner. I´m hosting the designer into my application and created state machine activities with more usability to create workflows. My final user can create workflows.
  2. Why not public classes?

  • Anonymous
    March 10, 2009
    Just last week I needed to use the private InvokeWorkflowDesigner to display a custom InvokeWorkflowActivity on a State Machine design surface.  I found that it was applied to the InvokeWorkflowActivity at runtime in both a tricky and inconsistent way.

  • Anonymous
    March 25, 2009
    The comment has been removed