Quote:
Originally Posted by Valloric
Please target it to .NET 2.0. I seriously doubt you need more than that. Always target the lowest numbered version that has all the features you want. With 3.5, your users will most definitely have to download and install the framework installer (even with Vista), whereas most computers today have .NET 2.0 by default.
Targeting it to 3.5 and using only features from 2.0 and lower has absolutely no advantages, but has several disadvantages.
|
Why do you think i'd target it at 3.5 and not use its features? Thing is I definately want to learn/use WPF. It's a beautiful framework that's half a decade ahead of winforms or anything else.
I've previously thought of doing a 2.0 class library, and then wrapping it in a 2.0 command-line tool along with the 3.5 gui. I would be careful to make the 2.0 parts portable with posix filenames, etc. I was going to use the same pipeline as 2.5, going out to the shell and and running the same command-line utilities.
What I found out recently, though, is that 3.5 SP1 is introducing a new feature that basically lets you use pixel shaders in WPF. If I offload the computations to the video card, I could really speed up rasterfarian's sorry performance. I have a bunch of experience writing pixel shaders, and it shouldn't be too much work if I can find what equations my tools use. Also, I found out that going out to the shell is a fairly dirty and/or inflexible business from C#.
What I might be able to do is to rewrite 2.5 into a cross-platform .net executable. Is there a demand for that?