A connect case regarding workflows hosted in IIS as been marked resolved as by design. See connect ID 558275 "Async Callback exception causes w3wp to crash when loading old instances of workflows in WorkflowServiceHost".
This seems like a really lame resolution to me. Is there any avenue of appeal for the design of this implementation? Does anyone else in the community share my distaste for the current harsh exception handling of tearing down the whole w3wp.exe
just due to an error in one particular .xamlx? I think this forum has better traffic than connect so I'm hoping that if a few more people get exposed to this issue the community can provide additional feedback that might be missed on connect.
I know that AppFabric is not yet RTM, so I hope there is still time to get this addressed maybe as part of the AppFabric release even if it requires a change in the core 4.0 bits. It seems like there is already a presumption that if you are hosting
in IIS you will use AppFabric so I would find it acceptable if the AppFabric release had a better more robust solution when a single workflow gets in a bad state.
Anybody else have any thou
View Complete Post