Hi,
Why does WorkflowWebRequestContext.Current always return null, and when I create a new instance of WorkflowRuntime i get the error saying that you cannot create more than one instance per appDomain
WorkflowWebRequestContext.Current always returns null
Hot Topic
- LoadLibrary (regsvr32) fails without Visual Studio 2005
- WorkFlow Projects not showing in VS 2005
- Vista 5308 Media Center Extender issues
- Install Issues - "a disk read error occurred"
- How can I get the designed graphical workflow into a Word document?
- Keybord Shortcuts - Big XP Bug
- Known Folders in Vista Beta 2
- Segoe UI
- WorkflowTrace.log being generated in Beta2
- Error message in state machine workflow. HELP!
Windows Vista
- Vista 5308 refuses to activate. Any way to retrieve files?
- Dyanamic State Work flow
- Overprint, knockout or trapping in XPS?
- ICredentialProvider
- At Last Got it !! [The Book Presenting Windows Workflow Foundation, Beta Edition in .chm ]
- VS 2005 final release vs. Windows Workflow Foundation
- WF custom persistence once again
- XAMLPad Problem
- Vista Download ?
- Keybord Shortcuts - Big XP Bug
WorkflowWebRequestContext.Current always returns null
gshaf
Check to make sure you have this line in your web.config
<
httpModules><
add type="System.Workflow.Runtime.Hosting.WorkflowWebHostingModule, System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" name="WorkflowHost"/></
httpModules>The WorkflowWebRequestContext.Current.WorkflowRuntime - is established from the http handler (above).
For e.g. you should be able to grab a non-null reference to it from within the App_Start - event within Global.ASAX.
So by the time your workflow runs, you should well and truly have a reference.
Are you exposing your WF as a Web.Service
Also - ******* if you use the ManualWorkflowSchedulerService ***** make sure you call the RunWorkflow(...) method from it!!!!! (after you RaiseEvents etc. etc.)
Let me know how you go.