> Of course, changes required to PowerSDR source between .NET 1.1 and
> 2.0 are trivial, as Phil already pointed out, and probably even the
> beginning programmer can learn how to make them. But having to do that
> with every new version that comes out is simply a nuisance.
>
> OK, maybe we can have it both ways. Let the official PowerSDR binary
> release remain .NET 1.1, but simply modify the source to make it
> compatible with the Visual Studio 2005 Express tools as well. But
> those modifications really have to be in the official PowerSDR source
> code instead of everyone having to make them on their own.
>
> It will probably require nothing more complex than a couple of
> #ifdef's, but I'll let someone more knowledgeable in .NET (Phil?)
> comment on this.
>
> 73, Sami OH2BFO
>

This is a sensible strategy and exactly what I hope happens.  That way, we
still have binary code that interfaces to 1.1.  That's what I most care
about.

The real question will be when someone desires to use the new function in
.Net 2.0.  IMHO, this had better be for something substantial, because it
will make a forced upgrade for a lot of people.  The fact that they can
still have 1.1 on their machine is nice, but not necessarily disposative. 
Adding a big chunk of new code often has unexpected consequences.  Some
nonSDR code, for instance, may adapt to what level(s) of .Net code is
available for all I know.  Whether easy or hard to do in .Net, such
practices have always existed.  That could make things unstable beyond our
own PowerSDR code.  For a typical user, it would be a great mystery if
this situation is even possible and something bad happened.

What is relevant is we have a very capable and proven software stack --
PowerSDR plus .Net 1.1.  If we change to PowerSDR plus .Net 2.0, I predict
addtional instability for some time to come on our own code base at least.

At the very least, this ought to be introduced as part of our beta/preview
work long before it becomes part of the "official supported" download.  In
the end, I think that will be easier for everyone, whenever we make the
move.

People need to plan this sort of thing a lot more often than is commonly
realized.


Larry WO0Z


Reply via email to