search

twcrane / aforge

Automatically exported from code.google.com/p/aforge
Other
0 stars 0 forks source link

.NET 4 support #258

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello!
Your project is amazing!

Please make adoptation for .NET 4.

Thanks!

Original issue reported on code.google.com by eiva...@gmail.com on 10 Oct 2011 at 7:34

GoogleCodeExporter commented 9 years ago 
What is wrong about .NET 4? What are the issues, which don't allow you to use 
the project in .NET 4 application?

Original comment by andrew.k...@gmail.com on 10 Oct 2011 at 7:38

GoogleCodeExporter commented 9 years ago 
Sorry, for mistake.
I mean: Please add controls for WPF not only for WinForms.
There a lot of differences in imaging components... this rises a lot of 
difficulties in integration with WPF.

Thanks!

Original comment by eiva...@gmail.com on 13 Oct 2011 at 7:11

GoogleCodeExporter commented 9 years ago

Original comment by andrew.k...@gmail.com on 24 Nov 2011 at 8:51

GoogleCodeExporter commented 9 years ago 
Thanks!

Original comment by Astel...@gmail.com on 25 Nov 2011 at 8:30

GoogleCodeExporter commented 9 years ago 
A port to .NET 4 could also be considered to take advantage of the Task 
Parallel Library. I know AForge.NET currently provides the Parallel class for 
parallel computations, but it doesn't offers as much flexibility as does the 
parallel library. For instance, marking Neuro/Network.cs "output" fields as 
ThreadLocal<double[]> (http://msdn.microsoft.com/en-us/library/dd642243.aspx) 
could potentially lead to better parallelizable learning algorithms for neural 
networks (currently, accessing the Output property after calling the network in 
multiple-threads is not thread-safe). 

The TPL can also handle calling parallel loops inside parallel loops. The inner 
loops would most likely be ignored and treated as normal loops. If I am not 
very wrong, the current framework approach doesn't work well in this scenario 
(but I may be wrong, didn't checked most recent releases).

Regards,
Cesar

Original comment by cesarso...@gmail.com on 4 Jan 2012 at 12:49

GoogleCodeExporter commented 9 years ago 
I don't mind of adding some support of WPF/.NET4, like WriteableBitmap. However 
I am not keen to port the framework completely to .NET4 so there is no way to 
use it in earlier frameworks. I am well aware of the fact that some of the 
users run the framework on systems like Embedded Windows with .NET 2.0. So 
complete port to .NET 4.0 would not be of use to them.

Original comment by andrew.k...@gmail.com on 8 Feb 2012 at 10:06

GoogleCodeExporter commented 9 years ago 
From what i've read about .net 4 and embedded systems, they too can get 
upgraded to .net 4.0 ( see here : 
http://www.microsoft.com/windowsembedded/en-us/catcatalog.aspx )

Original comment by peter.b...@gmail.com on 16 Feb 2015 at 3:06