Convert List or Collection to VisualBasicValue

Question

1.00/5 (1 vote)

See more:

Hi,

I was wondering if there is a way to convert a

C#

List<T>

to a

C#

VisualBasicValue<List<T>>

programmatically with reflection or something ?

At least with T is string or ValueType.

Thank you

Posted 29-Oct-15 6:06am

Christophe_

Add a Solution

Comments

Maciej Los 29-Oct-15 12:23pm

Christophe, it's not well-formed question...
Note, that List<t> is generic class, which supports filtering, sorting, etc.

Sergey Alexandrovich Kryukov 29-Oct-15 12:26pm

Why? What's wrong with List<t>?
I would strongly advise to avoid using anything VB-specific, use pure .NET FCL :-)
—SA

Maciej Los 29-Oct-15 12:36pm

Thank you, Sergey for your comment to my answer (deleted).
[EDIT]
I didn't realize that VisualBasicValue class exists!

Maciej Los 29-Oct-15 16:59pm

Check this: Authoring Workflows, Activities, and Expressions Using Imperative Code

Christophe_ 1-Dec-15 10:11am

Hi Maciej Los,

I want to add a List<string> (for example) as an argument to an activity (not the root activity) of my workflow. With WF4, if we use a non literal argument (ie something other than string or value types) we can't set its value, we need to use a VisualBasicValue or CSharpValue, I was wondering if we can convert a List to a VisualBasicValue programmatically because our workflows are designed by end user and I need that value to be stored in the workflow definition (not in a DynamicProperty from a DynamicActivity when running the workflow).

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)