[Coco] Preparing for a job which requires knowledge of C

[John Donaldson]

  I am just now starting to get a handle on VB.NET and C#. I kinda like 
C# better, since it is more like
the old C. There are some nuisances that you have to get used to, but 
once past that it gets easier. I
found that starting out writing small programs and then slowly add more 
complex stuff really helps. Also
there are a ton of FREE VB.NET and C# forums that really help. I was 
beating my head on the wall once trying to figure out how to use TABs 
under VB.NET and finially asked on one of the forums. That
 afternoon, not only did I get a reply but he add code to the reply that 
showe me how to do what I was
 trying to do.
  I have also found VB6.0 forums that really helps too. My current 
project at work is in VB6.0, so the
VB6.0 forums have been a real help. My last project was a VB.NET project 
that I had a working
Alpha and almost had the first Beta ready, when they decided to shelve 
it for the time being.
  I had a co-worker who is just getting into VB6.0 could not get a 
subroutine to return the result from a
varible passed to it. I looked at his code and said " use the word CALL 
in front of the subroutine".
He did and then it worked. All his previous work was in C. The old 
learning curve thinge. LOL

John Donaldson


zaphod at mchsi.com wrote:

>Even better, you could abandon Microsoft Visual Basic and use REALbasic from 
>www.realsoftware.com -- it's very much like VB6, but with improvements, and 
>capable of compiling for Macintosh OS, Windows, and Linux.
>
>I've tried VB.Net, and it's just too much. The compatibility libraries were 
>only included with Studio, a whole new learning curve, and way too much 
>overhead.
>
>
>  
>
>>I'm fairly certain that applications written in Visual Basic 6.0 will
>>continue running provided you can install the required run-time components
>>on these computers. I doubt the run-time components are installed with any
>>version of Windows, although I should note that I have a habit of wrapping
>>all of my applications in installation packages so I don't have to worry
>>about them.
>>
>>All versions of Visual Studio .NET include the Visual Basic 6.0 Migration
>>Wizard that converts Visual Basic 6.0 code to Visual Basic .NET code, but
>>the results vary widely depending on the specific application. I have some
>>applications that converted easily along with some applications that
>>allegedly converted but have so many compiler warnings and errors that it's
>>not worth the trouble. Code that relies on the Printers or Forms collection
>>won't work because Visual Basic .NET does not support these collections.
>>I've also had significant issues with code that uses default properties
>>(e.g. Label = "" instead of Label.Caption = "").
>>
>>I strongly recommend running the code through the Visual Basic 6 Code
>>Analysis tool before attempting to migrate the code to Visual Basic .NET.
>>This is a free tool from Microsoft that analyzes existing Visual Basic 6
>>code to identify some (but not all) potential problems that need to be
>>addressed prior to attempting to migrate the code to Visual Basic .NET.
>>
>>-----Original Message-----
>>From: coco-bounces at maltedmedia.com [mailto:coco-bounces at maltedmedia.com] On
>>Behalf Of KnudsenMJ at aol.com
>>Sent: Tuesday, April 18, 2006 7:52 PM
>>To: coco at maltedmedia.com
>>Subject: Re: [Coco] Preparing for a job which requires knowledge of C
>>
>> 
>>In a message dated 4/18/06 9:31:08 PM Eastern Daylight Time,  
>>johnadonaldson at sbcglobal.net writes:
>>
>>There is NO version after V6.0. It is NOW called Visual  Studio NET. 
>>Which is no where compatible
>>with the old VS5 or VS6. The  last word we got was VS6.0 (VB6, VC++6.0, 
>>and etc) support will be  discontinued as of Jan 2007. This mean no more 
>>updates or anything. VS5.0  was discontinued in 2004. Only the NEW .NET 
>>stuff will be  supported.
>>
>>
>>
>>OK -- I knew that MS was calling their all-in-one studio dot-NET, which  
>>seems to imply very Internet oriented (though maybe not).
>> 
>>But I trust that VB programs will still run on any Windows PC.  Or  won't 
>>they?
>> 
>>And if I ever upgrade to Studio NET, will it import my old projects?
>>Funny we should even have to ask these questions, but this is M$ we're  
>>talking about ... Mike K.
>> 
>>
>>-- 
>>Coco mailing list
>>Coco at maltedmedia.com
>>http://five.pairlist.net/mailman/listinfo/coco
>>
>>
>>
>>
>>-- 
>>Coco mailing list
>>Coco at maltedmedia.com
>>http://five.pairlist.net/mailman/listinfo/coco
>>    
>>
>
>  
>