xamlx

Add behaviorattribute to a WorkflowServiceHost

僤鯓⒐⒋嵵緔 提交于 2019-12-06 11:20:18
问题 Hi all i have a problem while adding a custom behavior to a WorkflowServiceHost. Here is my WorflowServiceHostFactory: public class ScoringWorkflowServiceHostFactory : WorkflowServiceHostFactory, IServiceHost<IKernel> { private static IKernel _InjectionInstance; public IKernel InjectionInstance { get { return _InjectionInstance ?? (_InjectionInstance = new StandardKernel(new ScoringWorkflowServicesNinjectModule(Scope))); } } public object Scope { get { return Guid.NewGuid(); } } public

Add behaviorattribute to a WorkflowServiceHost

醉酒当歌 提交于 2019-12-04 15:15:53
Hi all i have a problem while adding a custom behavior to a WorkflowServiceHost. Here is my WorflowServiceHostFactory: public class ScoringWorkflowServiceHostFactory : WorkflowServiceHostFactory, IServiceHost<IKernel> { private static IKernel _InjectionInstance; public IKernel InjectionInstance { get { return _InjectionInstance ?? (_InjectionInstance = new StandardKernel(new ScoringWorkflowServicesNinjectModule(Scope))); } } public object Scope { get { return Guid.NewGuid(); } } public override ServiceHostBase CreateServiceHost(string constructorString, Uri[] baseAddresses) { String

WF4 workflow versioning using WorkflowServiceHost

怎甘沉沦 提交于 2019-12-04 14:07:04
问题 Related to this question. I understand how to implement versioning of workflows using WorkflowApplication. If you keep the original XAML definition for older versions of your workflow around, you can load them using the right WorkflowApplication constructor. How could you ensure that WorkflowServiceHost uses the correct workflow definition when you want to host your workflows in IIS? There is a WorkflowServiceHost constructor that you can use to load a workflow definition, but when you are

WF4 workflow versioning using WorkflowServiceHost

我与影子孤独终老i 提交于 2019-12-03 08:53:10
Related to this question . I understand how to implement versioning of workflows using WorkflowApplication . If you keep the original XAML definition for older versions of your workflow around, you can load them using the right WorkflowApplication constructor. How could you ensure that WorkflowServiceHost uses the correct workflow definition when you want to host your workflows in IIS? There is a WorkflowServiceHost constructor that you can use to load a workflow definition, but when you are hosting inside IIS through a XAMLX file, you do not call WorkflowServiceHost yourself, this is handled