I'm, having problems running the Workflow Monitor sample.
It can query the workflows, but I get a big "X" on the rhs where it's supposed to display the workflow, and returns an error that says:
"Microsoft Workflow Designer"
"Object Reference not set to an instance of an object".
I'm using Beta 2.2.
Try rebuilding your tracking database. This will clear out any old data that might not be compatible with your current binaries. also, make sure you are putting updated copies of your workflow dll in the directory with the workflow monitor so it has copies that match what was tracked.
Matt
I've got them in the same directory. Locating the Workflow is not the problem.
It seems the problem is trying to display the workflow on the panel on the right. Something like hosting the deisgner or something? Is that what it does to display the workflow..host the designer?
I have the same problem with the sample workflow as well as my own workflow.
You may have some other items that are missing as references. For example, when I try to use the expense reporting sample application, not only did I have to copy in the workflows and activities, but I also had to add the contracts and local services dlls into the bin directory with the workflow monitor.
I'd look at the GetWorkflowDefinition method in MainForm.cs to locate the problem you are having. Exceptions get swallowed there so you might need to put a breakpoint to see what the problem is.
Matt
Have you been able to determine where hte exception is being thrown? If you run in debug mode can you find the exception details. The nice thing about this problem is we all have access to that application, so if you can point out the problem, we can help you find the cause.
Matt
This raises some interesting issues regarding making updates to custom workflow applications and/or updating WF framework components whilst there exists in-process workflows in the SQL store.
I imagine it will become good practice to only store simple (native CLR) types in an in-process workflow, and so alleviating the issue of changes to custom workflow binaries. i.e. just store an Order ID, not the serialised order instance itself. But what about changes to WF framework binaries - will there be tools to address state mismatch issues for insitu workflows ?
Problem is trying to run the WorkflowMonitor sample with the Tracking sample.
Exception is thrown at:
MonitorForm.vb line 513
Sub UpdateActivities
...
WorkflowViewHost.Refresh()
...
It won't work with any workflow I use.
I've also created my own workflow & have the exact same problem.
The workflows run etc. & the tracking DB has the info logged. It's just the viewing part of the Monitor.
It's like it can't host the Designer for some reason - install problem?
Is there a patch or something for this?
It was a clean VM I installed stuff to so there shouldn't be anything lying around from previous versions etc.
Cheers
What I find when I try the VB version is that the tracking instance coming back does not have an Instance ID correctly set, even when there is one in the database. I was not able to track down the exact location of the problem, but it seems like it might be a strange bug either in the SDK sample, or the bits.
I'd try - running the CS version, or testing the VB version in the June CTP to see if it works any better.
Matt
The CS Workflow monitor sample works fine for me.
The VB.NET one doesn't!!!!! AAarrrrgghhhg!!!!
