Home Dashboard Directory Help

Incorrect error message when property binding using a custom type in a ReceiveActivity by Maurice de Beijer - DevelopMentor


Status: 

Closed
 as Won't Fix Help for as Won't Fix


6
0
Sign in
to vote
Type: Bug
ID: 334555
Opened: 3/26/2008 10:14:19 AM
Access Restriction: Public
0
Workaround(s)
view
4
User(s) can reproduce this bug

Description

In the attached project I am property binding to the property TheForecast of type WeatherClient.WeatherService.ForeCast. This type is generated by the WCF proxy from the WeatherService in the solution.
The code runs just fine but the ReceiveActivity complains about the types not matching up and displays the following error message: Path resolved to Referenced activity Property “TheForecast” whose PropertyType ‘WeatherClient.WeatherService.ForeCast’ does not match with the Target Type ‘WeatherClient.WeatherService.ForeCast’.
Details
Sign in to post a comment.
Posted by Manuj Aggarwal on 2/5/2009 at 7:51 PM
Similar issue here.
Posted by Microsoft on 4/15/2008 at 8:18 AM
Dear customer, we identified this issue as a problem in Windows Workflow Foundation 3.5. The two types that are being compared came from two different type systems, which results in the error at design time. This however does not affect the compilation of the workflow, so the error is more superficial than prohibiting and can be ignored in most scenarios.

If you need further assistance on this issue or if you’re blocked by this, please contact PSS and we will conduct a more formal investigation. The link for PSS is http://support.microsoft.com/gp/contactbug.
Posted by Anonymous222222222222222222 on 4/7/2008 at 11:40 AM
I was able to get around this issue by including the interface in the same project as the workflow (I had my interface in a separate project).
Posted by Anonymous222222222222222222 on 4/7/2008 at 8:14 AM
I am experiencing the same problem. If anybody has any pointers please let me know.
Posted by Microsoft on 3/31/2008 at 1:57 AM
Thanks for your response. We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Thank you,
Visual Studio Product Team
Posted by Maurice de Beijer - DevelopMentor on 3/30/2008 at 11:02 AM
I can reproduce this without any problems on different PC using different Windows versions. See the attached screenshots don using Windows XP SP2. I have also seen this using Windows Vista. See also the screenshots I uploaded. For the screen shots I was using:
Microsoft Visual Studio 2008
Version 9.0.21022.8 RTM
Microsoft .NET Framework
Version 3.5

Maurice
Posted by Microsoft on 3/27/2008 at 12:36 AM
snapshot_kylin.jpg
Posted by Microsoft on 3/27/2008 at 12:19 AM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the project you provided. We tried to repro with the following steps:

1. Tried to reproduce this issue on Windows XP SP2 with VS2008 RTM
2. Tried to reproduce this issue on Windows Server 2008 Ent x64 with VS2008 RTM

It may help if you provide us with:

1. version of VS used.
2. more snapshots.

If we do not receive a response from you after 7-days , we will automatically close your issue. There is no obligation to respond -- at any time you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Sign in to post a workaround.