Click here to Skip to main content
15,887,485 members
Home / Discussions / Visual Basic
   

Visual Basic

 
AnswerRe: C# to VB Adaption Problem Pin
Eddy Vluggen1-Jan-12 6:23
professionalEddy Vluggen1-Jan-12 6:23 
GeneralRe: C# to VB Adaption Problem Pin
Sonhospa1-Jan-12 6:34
Sonhospa1-Jan-12 6:34 
GeneralRe: C# to VB Adaption Problem Pin
Eddy Vluggen1-Jan-12 6:39
professionalEddy Vluggen1-Jan-12 6:39 
GeneralRe: C# to VB Adaption Problem Pin
Sonhospa1-Jan-12 6:58
Sonhospa1-Jan-12 6:58 
AnswerRe: C# to VB Adaption Problem Pin
Eddy Vluggen1-Jan-12 7:36
professionalEddy Vluggen1-Jan-12 7:36 
GeneralRe: C# to VB Adaption Problem Pin
Sonhospa1-Jan-12 7:53
Sonhospa1-Jan-12 7:53 
GeneralRe: C# to VB Adaption Problem Pin
Eddy Vluggen1-Jan-12 8:35
professionalEddy Vluggen1-Jan-12 8:35 
GeneralRe: C# to VB Adaption Problem Pin
Sonhospa1-Jan-12 12:16
Sonhospa1-Jan-12 12:16 
From my initial message:
Michael Schäuble wrote:
In order to avoid problems with conversion of c# 'yield' operator, I put the extensions into a DLL and set a reference to that.
According to IntelliSense 'progress' should be an integer value for 'percentProgress'.

The funny thing is that it works as described as long as I stay in C# with the Main procedure - also when using the same referenced DLL for all the extensions:
items
    .WithProgressReporting(progress => worker.ReportProgress(progress))
    .ForEach(item => Thread.Sleep(10)); // simulate some real work
Line 2 results in the percentage, which is properly reported to the console. So there really must be something wrong with the lambda, which obviously is too cryptic for me... Still this is exactly the part of the code which I can't reference (main procedure "TestProgressReporting") since my application is written in VB.

modified 1-Jan-12 18:42pm.

AnswerRe: C# to VB Adaption Problem Pin
Luc Pattyn1-Jan-12 12:33
sitebuilderLuc Pattyn1-Jan-12 12:33 
GeneralRe: C# to VB Adaption Problem Pin
Sonhospa1-Jan-12 12:51
Sonhospa1-Jan-12 12:51 
AnswerRe: C# to VB Adaption Problem Pin
Luc Pattyn1-Jan-12 12:58
sitebuilderLuc Pattyn1-Jan-12 12:58 
GeneralRe: C# to VB Adaption Problem Pin
Sonhospa1-Jan-12 13:14
Sonhospa1-Jan-12 13:14 
GeneralRe: C# to VB Adaption Problem Pin
Eddy Vluggen2-Jan-12 6:34
professionalEddy Vluggen2-Jan-12 6:34 
GeneralRe: C# to VB Adaption Problem Pin
Terence Wallace3-Jan-12 7:32
Terence Wallace3-Jan-12 7:32 
AnswerRe: C# to VB Adaption Problem with Lambda Expressions Pin
Simon_Whale2-Jan-12 12:33
Simon_Whale2-Jan-12 12:33 
GeneralRe: C# to VB Adaption Problem with Lambda Expressions Pin
Sonhospa9-Jan-12 23:09
Sonhospa9-Jan-12 23:09 
GeneralRe: C# to VB Adaption Problem with Lambda Expressions Pin
Simon_Whale9-Jan-12 23:12
Simon_Whale9-Jan-12 23:12 
AnswerRe: C# to VB Adaption Problem with Lambda Expressions Pin
Member 78595873-Jan-12 2:58
Member 78595873-Jan-12 2:58 
GeneralRe: C# to VB Adaption Problem with Lambda Expressions Pin
Sonhospa9-Jan-12 23:15
Sonhospa9-Jan-12 23:15 
AnswerRe: C# to VB Adaption Problem with Lambda Expressions Pin
Estys3-Jan-12 4:03
Estys3-Jan-12 4:03 
GeneralRe: C# to VB Adaption Problem with Lambda Expressions Pin
Sonhospa9-Jan-12 23:19
Sonhospa9-Jan-12 23:19 
GeneralRe: C# to VB Adaption Problem with Lambda Expressions Pin
Estys9-Jan-12 23:50
Estys9-Jan-12 23:50 
AnswerRe: C# to VB Adaption Problem with Lambda Expressions Pin
DavidSherwood3-Jan-12 16:56
DavidSherwood3-Jan-12 16:56 
GeneralRe: C# to VB Adaption Problem with Lambda Expressions Pin
Simon_Whale3-Jan-12 21:51
Simon_Whale3-Jan-12 21:51 
GeneralRe: C# to VB Adaption Problem with Lambda Expressions Pin
Sonhospa9-Jan-12 23:22
Sonhospa9-Jan-12 23:22 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.