Working with beta2, if I try to add SqlWorkflowPersistenceService to my webconfig, the WorkflowWebRequestContext.Current become null in my aspx page.
Then if
I add only ManualWorkflowSchedulerService and
DefaultWorkflowTransactionService, without adding
SqlWorkflowPersistenceService, WorkflowWebRequestContext.Current isn't null
and WorkflowWebRequestContext.Current.WorkflowRuntime is succesfully
loaded.
How could I add the SqlWorkflowPersistenceService
This is my web config file
< xml version="1.0" >
<!--
Note: As an alternative to hand editing this file you can use the
web admin tool to configure settings for your application. Use
the Website->Asp.Net Configuration option in Visual Studio.
A full list of settings and comments can be found in
machine.config.comments usually located in
\Windows\Microsoft.Net\Framework\v2.x\Config
-->
<configuration>
<configSections>
<section name="WorkflowRuntime"
type="System.Workflow.Runtime.Configuration.WorkflowRuntimeSection,
System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>
<appSettings/>
<connectionStrings>
<add name="TirocinioConnectionString" connectionString="Data
Source=pcmobile;Initial Catalog=Tirocinio;Integrated Security=True"
providerName="System.Data.SqlClient" />
</connectionStrings>
<system.web>
<!--
Set compilation debug="true" to insert debugging
symbols into the compiled page. Because this
affects performance, set this value to true only
during development.
-->
<httpModules>
<add name="WorkflowHost"
type="System.Workflow.Runtime.Hosting.WorkflowWebHostingModule,
System.Workflow.Runtime, Version=3.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
</httpModules>
<compilation debug="true">
<assemblies>
<add assembly="System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Transactions, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.Workflow.Activities,
Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Workflow.ComponentModel,
Version=3.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="System.Workflow.Runtime, Version=3.0.0.0,
Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>
<add assembly="Microsoft.Build.Tasks, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Messaging, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Runtime.Remoting, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="System.DirectoryServices, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
<add assembly="Microsoft.Build.Utilities,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
<add assembly="Microsoft.Build.Framework,
Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>
</assemblies>
</compilation>
<!--
The <authentication> section enables configuration
of the security authentication mode used by
ASP.NET to identify an incoming user.
-->
<authentication mode="Windows" />
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
<customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
<error statusCode="403" redirect="NoAccess.htm" />
<error statusCode="404" redirect="FileNotFound.htm" />
</customErrors>
-->
</system.web>
<WorkflowRuntime>
<Services>
<add
type="System.Workflow.Runtime.Hosting.ManualWorkflowSchedulerService,
System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
<add
type="System.Workflow.Runtime.Hosting.DefaultWorkflowTransactionService,
System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35"/>
<add
type="System.Workflow.Runtime.Hosting.SqlWorkflowPersistenceService,
System.Workflow.Runtime, Version=3.0.00000.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" connectionString="Initial
Catalog=WorkflowPersistenceStore;Data Source=localhost;Integrated
Security=SSPI;" UnloadOnIdle="true"/>
</Services>
</WorkflowRuntime>
</configuration>
WorkflowWebRequestContext.Current is null with SqlWorkflowPersistenceService
Hot Topic
- Editor for creating/editing XPS documents.
- DwmEnableMMCSS
- How to use DirectShow to save a vidieo as a file of frames?
- Custom control patterns
- problems communicating with the host
- Problems with the rules expressions binding when using the GUI.
- Package Load Failure
- SampleGrabber not working with NullRenderer
- Changing activities Id's
- Welcome Tablet PC/Mobile PC users and the world!
Windows Vista
- Windows Vista CTP - 64-bit - Build 5231 Install Problems
- January CTP - no Activities in the Toolbox
- Vista UI lacks of Transitions, Fades and some other things
- Is there a Certificate Authority server available in Vista?
- hi james ,about your asp.net web apps
- Any Utils Available To Sync Activities With SqlTrackingService?
- Designer re-hosting and XAML only workflows
- K2.NET vs WWF
- SETUP.EXE throwing unhandled exception while installing Vista
- Is simultaneously displaying live captured video and its processed version possible?
WorkflowWebRequestContext.Current is null with SqlWorkflowPersistenceService
Raul Garcia - MS
TommieLand