C# is the native language...

Post #244,074 by ChrisR 2/9/06 9:31:15 PM Reply	C# is the native language... ...so I figure that it's the best language for the .Net platform. All the other languages have to do some bending, with mixed results. That said, the programming language being used is really tertiary, falling behind the APIs and the developer IDE. In the same respect that Java is a slave to the APIs and the IDEs (like Eclipse), C# is a dependent on the framework APIs and Visual Studio. For C#, I've probably read half a dozen books, and come away from most with glazed eyes - they are either too slow or they are little more than printed API documentation. Only book that I can recommend would be [link\|http://www.amazon.com/gp/product/0596006993/103-9342776-6096602\|Programming C#]. From the same author comes [link\|http://www.amazon.com/gp/product/059600916X/103-9342776-6096602\|Programming ASP.Net] which is also not terrible (though I disliked the earlier additions of the book, he finally got a bit better in the last one). Of course, if you just want the cliff notes, you can check out my cheat sheets for [link\|http://www.angelfire.com/tx4/cus/notes/csharp-syntax.html\|C#] and [link\|http://www.angelfire.com/tx4/cus/notes/aspnet.html\|ASP.Net].
Post #246,675 by lincoln 3/3/06 12:15:07 PM Reply	Stick with C# As I'm new to the web design world, and my company is a MS shop, I'm using ASP.Net to build screens - VB.Net is the "code behind" that does the actual work. One of our contractors puts some Javascript in the actual .aspx screens that he creates (and that's on my list of things to learn next). I've been contacted by a few recruiters lately who say that, because of the demand for C# programmers, people who know VB.Net are actually becoming more "of value" because of their rareness. Yet everyone that I've talked to say that MS is pushing to move everybody to C# and eventually phase out VB. My newbie view. lincoln "Chicago to my mind was the only place to be. ... I above all liked the city because it was filled with people all a-bustle, and the clatter of hooves and carriages, and with delivery wagons and drays and peddlers and the boom and clank of freight trains. And when those black clouds came sailing in from the west, pouring thunderstorms upon us so that you couldn't hear the cries or curses of humankind, I liked that best of all. Chicago could stand up to the worst God had to offer. I understood why it was built--a place for trade, of course, with railroads and ships and so on, but mostly to give all of us a magnitude of defiance that is not provided by one house on the plains. And the plains is where those storms come from." -- E.L. Doctorow Never apply a Star Trek solution to a Babylon 5 problem. I am not merely a "consumer" or a "taxpayer". I am a *Citizen* of the United States. [link\|mailto:bconnors@ev1.net\|contact me]
Post #246,680 by ChrisR 3/3/06 12:49:42 PM Reply	VB.Net won't get phased out It'll just eventually be morphed into C# with different syntactic sugar. The languages are so much alike that [link\|http://www.icsharpcode.net/OpenSource/SD/\|SharpDevelop], the open source equivalent to visual studio, claims to be able to translate [link\|http://en.wikipedia.org/wiki/SharpDevelop\|VB to C#] and vice versa. As for the next big thing in the .Net world, no doubt it will be [link\|http://msdn.microsoft.com/netframework/future/linq/\|LINQ]. Though, I'm not sure how well that will play with the business object frameworks like Neo.
Post #246,790 by JayMehaffey 3/4/06 12:20:31 PM Reply	That is what I'm hearing Talked to several people at firms that do contracting. They are all biting on the C# experience on the resume. From what they tell me the only people doing VB.NET are companies that switched from VB, and those are slowly moving to C#. Jay

Welcome to IWETHEY!