> Hmmm... I have routinely built PowerSDR with .NET 2.0 since the first > beta. > The current release compiles fine in .NET 2.0 with VS 2005. Other than a > few > minor changes to the source code (Math.Floor) it is completely > straightforward. The only thing noticeable is that the CPU utilization > goes > down slightly due to the optimizations in the JIT compiler for 2.0. > > For people who pay attention to such things, there are very good reasons > for > using .NET 2.0 - one minor one being that the SerialPort Class now comes > with .NET 2.0 so my separate SerialPort class used in PowerSDR can be > dumped > in favor of it. > > I would think that a lot of guys would be happy that they can download C# > 2005 Express for free to build PowerSDR instead of having to pay for full > blown VS 2003. >
I may well do that. But, that's different than the way I treat production code. If all I did on my PC was run browsers, e-mail and SDR, that would be fine. But, I do a lot more than that. And, I integrate big software projects for a living. I've long ago learned that even the most benign looking change has more risk than meets the eye. The darndest things eventually happen. Other bits of code don't always do the obvious and easy thing. If there are two choices in how to handle an upgrade situation, both get implemented by someone and if one goes bad, then the code it represents goes bad. That's why I don't see the need for haste, here. Besides, I find your serial port code very stable. Why should I be eager to replace it? You work is very good -- I haven't needed any upgrades -- it has been very stable for me. We don't need to be the leading edge everywhere. At least, not all of us. Larry WO0Z
