Hi All,
I'm writing a project using TPL Dataflow Library to see if it would be a better long term solution for real time data processing. (it seems like it will be)
I've added the reference: System.Threading.Tasks.Dataflow and when I define any block it requires that I explicitly add a system.runtime reference to the project.
This seems like a dangerous practice (in case the final user updates the framework etc.); is there any reason I've had to add this reference explicitly?
I've pretty much written the same code in C# and I DO NOT have to add a reference to System.Runtime. Is this a problem with VB?
Nick
I'm writing a project using TPL Dataflow Library to see if it would be a better long term solution for real time data processing. (it seems like it will be)
I've added the reference: System.Threading.Tasks.Dataflow and when I define any block it requires that I explicitly add a system.runtime reference to the project.
This seems like a dangerous practice (in case the final user updates the framework etc.); is there any reason I've had to add this reference explicitly?
I've pretty much written the same code in C# and I DO NOT have to add a reference to System.Runtime. Is this a problem with VB?
Nick