locked
Should I worry about these: "Does not have corresponding Xaml node for: VisualBasicValue`1" RRS feed

  • Question

  • I'm working with a Declarative Sequential Service Library.  When I call into it, I see these:

    Does not have corresponding Xaml node for: VisualBasicValue`1

    Does anyone know if they are the result of something I haven't done or just a beta 1 issue?  They seem to occur both when my workflow works and when it doesn't.


    Friday, October 2, 2009 8:15 AM

Answers

  • I think its just a Beta 1 issue as I have also faced such issue but my workflow was still working fine
    • Marked as answer by SSG31415926 Friday, October 2, 2009 5:15 PM
    Friday, October 2, 2009 2:09 PM

All replies

  • I think its just a Beta 1 issue as I have also faced such issue but my workflow was still working fine
    • Marked as answer by SSG31415926 Friday, October 2, 2009 5:15 PM
    Friday, October 2, 2009 2:09 PM
  • Okay, thanks for the reply.
    Friday, October 2, 2009 5:15 PM
  • I have a similar issue, except mine is:

    Does not have corresponding Xaml node for: VisualBasicValue<Boolean>
    Does not have corresponding Xaml node for: VisualBasicValue<Object>
    Does not have corresponding Xaml node for: Literal<String>

    Workflow still works fine for me except it takes longer to debug while it writes all these messages to the output window.
    * Note: I have no formal CS education, so take all advice with caution :)
    Friday, February 19, 2010 10:31 PM