C# training courses

[chim_knee]

Hi,

Does anyone have any experience of training companies in C#? (BTW What's the consensus on my next step as a VB6 developer? C# or .Net - not interested in Java though).

I am based in EC2 in London so if anyone has experience of a company that is relatively local - that would be great.

What's the recommendation for a VB6 developer to x-train to C#? I have been told to do "an intro to C#" and follow that with something like "OO programming with C#". I have a reasonable idea of OO methods but could definitely benefit from a brush-up/advancement.

TIA,
Phil.

[robdickinson]

c# is .net, cant realy do one without the other I would have thought. You could have a play with vb.net and see what the .net thing is all about , thus leaving you only the c# bit to cover.

From VB6 i'd say an into course would be best, the C(#) syntax can be a bit of a shock at first tho c# is easier to get a grips on, but you havnt done much oo either eh?

>> Edited by robdickinson on Thursday 16th December 12:02

[gopher]

If you have not done much oo then it may well be worth you getting a course in oo design before you worry too much about the coding. It is different and may bog you down when you first get started with .net. I have noticed a number of examples, even on so called expert web sites, that are basically vb 6 programs (style wise) written within the .net framework, certainly not the way to go.

I really would urge you to download the .net sdk here

www.microsoft.com/downloads/details.aspx?familyid=9B3A2CA6-3647-4070-9F41-A333C6B9181D&displaylang=en

if you haven't already and get to know what classes are in the libraries (they are very rich) and code a few examples in vb.net and c#.

As far as what language you choose they are very much the same as they all use these libraries as a basis, syntactically they differ, vb.net is more verbose and not to my liking.

I came from a vb6 asp scripting background and did quite a lot with javascript and as I found a preference for javascript choose c# as it more closesly resembled this, either way assemblies in one language should work seemlessly with those from another .net language (cobol.net anyone?).

Good luck.

[JonRB]

I can't comment on cross-training from VB6 to C#, but as an OO C++ developer cross-training to C# I would recommend this book.



The style is good, and it has very useful break-out boxes all over the place saying "C & C++ developers - note this", "VB6 developers - read this" to highlight the differences between the languages, which is exactly what I was looking for.

>> Edited by JonRB on Thursday 16th December 12:52

[chim_knee]

Thanks guys - the more I look in to this the more sense(ish!) it makes. I realise now that .net is a framework and, as you've said, C#/vb.net is just the syntax for utilising that.

I wonder what I need to do with OO. I studied it at Uni and I have a good idea of the basics (inheritence, polymorphism, encapsulation and so on) but I do think further study would be beneficial. It feels a bit like the chicken/egg situation - as maybe an OO with C# would be good but should I know C# a bit first and therefore do C# first - or would I be confused by C# if I haven't done OO first!! Aaarghh!

I think that's a fair point gopher about my leaning would probably be to try and code .net in a VB6 style... "starting again" would probably be the best idea. Thanks for the link - will do!

Thank JonRB for the book - I'll take a look.

Now - sadly for you guys, you've just publicly admittied you know about C# et al...... expect a few more questions on here in the near future!!

Thanks again all.

[ThatPhilBrettGuy]

Another tip. DO NOT convert VB6 projects to VB.NET ones. Start again. The converter, whilst it works, doesn't, IMHO, create nice code.

[gopher]

chim_knee said:

I wonder what I need to do with OO. I studied it at Uni and I have a good idea of the basics (inheritence, polymorphism, encapsulation and so on) but I do think further study would be beneficial. It feels a bit like the chicken/egg situation - as maybe an OO with C# would be good but should I know C# a bit first and therefore do C# first - or would I be confused by C# if I haven't done OO first!! Aaarghh!

If you've studied oo before it may be worth just dusting off those old notes and giving it a try, the biggest problem is for people that have only used non oo methodologies, they can stuggle with the whole "paradigm shift", but having already had exposure you could use the framework to help build on this knowledge.

P.S Agree with JohnRB about the book, 'tis a good one.

[jlanng]

As others have implied, it isn't the semantics of the language so much as learning about the CLR.

www.andymcm.com/dotnetfaq.htm

[chim_knee]

Thanks all - plenty of reading ahead, then!

>> Edited by chim_knee on Friday 17th December 08:55