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

[Kunle O. <kun...@vi...>]

> Hi!

Hi David,

> I think that the best for the project Eclipse .NET is to=20
> integrate and=20
> explore .NET 2.0 framework?s functionalities as soon as=20
> possible. It is=20
> not a question of following the high tech hype.

You are right of course.

I see improvements to the AppDomain bits (particularly cross-domain =
calling
performance) as important given our framework of loadable/unloadable =
plug-in
architecture.

> As my other colleagues referred, it?s a matter of recognizing the=20
> benefits that this framework brings to the developer in terms=20
> of C# 2.0=20
> and the productivity gains by using VS2005. Despite that I?m=20
> not using=20
> currently these in my prototype, I?m planning to integrate them soon.
>=20
> Besides that, if the hole community (Microsoft and Mono Project) is=20
> making the change I thing that resisting to .NET 2.0 is contributing=20
> for Eclipse .NET to become outdated.

Yep.

> Jo=E3o has already made some changes not because the hype but=20
> especially=20
> for his own profit in terms of developing facilities. He also had the=20
> determination to reason carefully about what you said and=20
> presented us=20
> with a detailed logical explanation that convinced me more about the=20
> need of this change.

Welcome to the dark side  ;-)

I'm drifting back to my original position that .NET 2.0 is cooler than =
warm
tequila.

> For me integrating .NET 2.0 is for the best. Besides no one likes to=20
> ?pass from horse to donkey? this is a bad translation from a=20
> Portuguese=20
> saying, but I think you?ll understand ?

Yeah, I can imagine. Proverbs are short sentences drawn from long =
experience
so, I concur. Let's ride the horse and lose the donkey.

Kunle