Posts from — June 2010

This is a Neo-Geo AES cartridge:

What this picture fails to show is the scale of this cartridge.  Just looking at it, you might think that the cartridge is roughly the size of a Super Nintendo cart.

You’d be wrong.

It is, in fact, roughly the size of TWO Super Nintendo cartridge stacked together and placed next to TWO NES cartridges.  Seriously.  They’re that massive.

And I thought that the Fairchild Channel F carts were bulky…

Given that I spent all day looking for this and had trouble finding it (Okay, I’ll be honest, I skipped a page in the book because it didn’t look relevant, but whatever), if you ever need to get the name of the currently executing state on a Windows Workflow (WF) State Machine Workflow, there’s a class you can use called StateMachineWorkflowInstance.  StateMachineWorkflowInstance has a property called CurrentStateName to give you the name as a string and another called CurrentState, which gives you an instance of the StateActivity object that’s currently running.

For some reason unknown to me, StateMachineWorkflowInstance isn’t derived from WorkflowInstance ((Cause, you know, .Net is all object orienty and such, so that’s what I would’ve done…)), so the WorkflowInstance you get back from WorkflowRuntime.CreateWorkflow can’t be cast to a StateMachineWorkflowInstance instance.  Instead, you have to new up the object yourself.  The constructor takes the WorkflowRuntime where the workflow is executing, and the Guid returned by the InstanceId property on the WorkflowInstance that was returned by CreateWorkflow for the workflow you want to know the state for.