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.

Phil N8VB


On 11/10/05, Larry Loen <[EMAIL PROTECTED]> wrote:
Sami Aintila wrote:

>Eric,
>
>
>
>>of fact VS 2003 won't compile for .NET 2.0 unless some things are changed.
>>You would have to use VS 2005.
>>
>>
>
>But now that the Visual Studio 2005 Express Editions have also been
>officially released, what are the plans to migrate PowerSDR to .NET
>2.0?
>
>I know a lot of folks are always very apprehensive of "the latest
>thing from Microsoft" whatever that may be. But having chosen C# as
>programming language and .NET as platform for PowerSDR development,
>this surely can't be FlexRadio's position.
>
>

As a matter of fact, it can and probably should be.  Not everyone is on
the instant Microsoft upgrade wagon, particularly hams.

Not me, that's for sure.

I don't want to upgrade anytime soon and I hope Flex won't force it upon
us all.  Things seem to be working just fine at this level of code and I
don't see why we need to jump every time Redmond wants to upgrade.  Its
needs and wants need not be ours.  And, as a matter of fact, Microsoft
itself recognizes this.  I'm sure this level of code will have official
support for years to come.  It always has before.

We need be in no hurry.  We're merrily experimenting, changing lots of
variables in our own stuff.  But, .Net has been very stable.

Let someone else debug the latest .Net -- we have our own work to do.

Plenty of time to talk about upgrades.  I still haven't got my money's
worth out of the current level of Visual Studio anyway.  But, if I
didn't own the development package, but just the .Net runtime, I'd be
even more apprehensive about it.  Why mess with working code?  What's
the rush?



Larry WO0Z



_______________________________________________
FlexRadio mailing list
FlexRadio@flex-radio.biz
http://mail.flex-radio.biz/mailman/listinfo/flexradio_flex-radio.biz



--
Philip A Covington
http://www.philcovington.com



--
Philip A Covington
http://www.philcovington.com

Reply via email to