Error:"Currently selected property has a wrong type"

I was working on a WF project and all of the sudden I started receiving the following error message when using the WF Designer in Beta 2.2:

''Currently selected property has a wrong type 'WF.wfEventArgs instead of 'WF.wfEventArgs'

Here's the fun thing. The types are the EXACT SAME TYPE. It is expecting what I provide it and it fails.

Has anyone experienced this?

Thanks.

[414 byte] By [PeterY] at [2007-12-21]
# 1

Peter,

Did you upgrade from Beta 2.0 to Beta 2.2?

This error message looks like you have a mismatch in Workflow DLL's or the runtime itself.

BillZunis at 2007-9-10 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 2

I did upgrade from 2.0 to 2.2 and this was/is my first suspicion. I did follow the instructions for removing the 2.0 beta, but I wonder now if something was left.

It is good to know that my suspicions may be confirmed. Maybe I can convince my boss to let me take a day to wipe and re-build my machine.

PeterY at 2007-9-10 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 3

One thing to try is to delete all of the Workflow Assembly references from your project and then re-add them. Please give this a try and see if this fixes it.

Steve Danielson [Microsoft]
This posting is provided "AS IS" with no warranties, and confers no rights.

SteveDanielson at 2007-9-10 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 4

I always get this message box... Just close it and retry, usually works for me...

100% a bug...

Never compare 2 types using == operator... Instead use Equals which works just fine...

AlexeyLavnikov at 2007-9-10 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 5
Make sure the Extensions, and then the actual Workflow Foundation last. then re-install Beta 2.2
BillZunis at 2007-9-10 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 6
Nope. That did not do it. I even tried it from 2 different developer stations.
PeterY at 2007-9-10 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...
# 7

Ok. That is enabling me to continue with designing the workflow.

I gather that you have not seen any negative effects because of this?

PeterY at 2007-9-10 > top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...

Software Development for Windows Vista

Site Classified