RE: [Eclipsedotnet-developers] .NET 1.1 vs .NET 2.0 again

[<jpp...@gm...>]

 

> Not really. We just have to decide and bite the bullet. We don't *need*

> .NET

> 2.0 (or C# 2.0) to build the platform but, we might prefer to target it

> anyway if it boosts our productivity for instance.

 

Agreed.

Frankly, I tend towards picking .NET 2.0, not because of the IDE or because
of Generics (the parts of the platform that use generics can be easily
adapted to use normal collections, it's just a matter of 1 or 2 days' work,
as I previously mentioned), but because the .NET 2.0 framework can load .NET
1.1 assemblies. So, if one has plugin dlls made in 1.1, those can be used
without problems. The opposite (.NET 1.1 using 2.0 assemblies) is not true,
and forces the developer to use 1.1 (most shouldn't find that a problem, but
there may be cases that do).

However (and this just came to my mind right now), this "advantage" can turn
out to be a disadvantage: if the platform assemblies are made in 2.0,
developers that (re)compile their assemblies must use the 2.0 compiler (not
the 1.1). The reason is that the compiler will need to access referenced
assemblies in compile time, and so it must be able to load those referenced
assemblies (in 2.0).

 

 

And, on a personal opinion, I do think that .NET 2.0 (especially generics)
can greatly improve developer productivity. Just yesterday, I corrected some
bugs (in the SWT_UI solution) that would never have gotten there in the
first place if I had generics when I first made the code :( . BTW, the
preferences dialog should now show all pages without throwing the infamous
"There was an error alerting a preference listener." :D .

 

 

But VS2003/2005 can still be a big pain in the butt. That's why I have in my
next TODO tasks to take a deep breath and look at Nant, to add the scripts
to build the assemblies (therefore bypassing VisualStudio and removing the
need for it).

 

 

JS