From: "Robert Comer" 

>I think I don't want to learn VB.Net, if I'm gonna use .Net I'd rather
> learn C# so I keep my VB 6 chops.

C# and vb.net aren't all that different, and I learned my VB6 chops the
hard way -- by mod'ing programs already built.  I went back to square one
for vb.net and I wont look back.

I have production VB6 apps in a three tier client server app, but I'm going
to move the middle tier onto the backend machine (and AS/400) and make the
client side a lot lighter too, so any programming I do on it will be all
new.

If I could have converted my VB6 code straight into vb.net, I wouldn't be
doing it this way. :(

>TOH it looks like we're going to be
> using both Java and .Net, so I guess if I do C# I will probably get
> mixed up with Java.  

I bet not, you'll be able to keep it straight.

- Bob Comer


"Ellen K."  wrote in message
news:7i4r81td82lud4103dl23m4ocq0bsio7ts{at}4ax.com...
>I think I don't want to learn VB.Net, if I'm gonna use .Net I'd rather
> learn C# so I keep my VB 6 chops.  OTOH it looks like we're going to be
> using both Java and .Net, so I guess if I do C# I will probably get
> mixed up with Java.  
>
> On Mon, 16 May 2005 20:39:50 -0400, "Robert Comer"
>  wrote in message :
>
>>I'm actually starting to program in it.  It's not so bad, but they made
>>some
>>serious mistakes in the transition from visual basic to visual basic.net.
>>
>>- Bob Comer
>>
>>
>>"Richard B."  wrote in message
>>news:hn3i81h4om7tr8ut73datmb4babuodlui3{at}4ax.com...
>>> On Mon, 16 May 2005 16:10:30 -0400, "Geo."
 wrote:
>>>
>>>>I think I was right to avoid .NET stuff and will continue to do
>>>>so on all my other machines.
>>>
>>> I've had other software require it to be installed, some engineering
>>> software (Haested) did.
>>>
>>> - Richard
>>
>

--- BBBS/NT v4.01 Flag-5