[MANASWIMEHARKURE]

ANY IDEA OF TUTORIALS !!!!!!!!!!!
I MEAN BEST BETWEEN VB.NET,C# AND ALL THAT...

This post has been edited by MANASWIMEHARKURE: 20 July 2011 - 07:57 PM

[fromTheSprawl]

C# is the way to go, unless you have more experience with VB.
Uh experts, am I right? Haven't tried VB yet.

[JackOfAllTrades]

Moved to .NET Framework.

We have tutorials on C# and VB .NET.

Then there's always a search engine, like, say Google.

[Jeff H]

Does not matter.

Learn F#

[modi123_1]

Learn both VB.NET and C# - problem solved.

[Sergio Tapia]

I wouldn't recommend F# for a beginner.

A) You can't find much work unless you really know the language. Most people get scared of functional programming.

B ) What you learn doesn't apply well to other traditional languages, so you would be making it harder for yourself to try a second language a year down the road.

C# gets a +1 from me, I just find VB.Net a bit...dirty. I don't know. I just don't like it.

This post has been edited by Sergio Tapia: 20 July 2011 - 08:58 PM

[eclipsed4utoo]

Neither is better. Both can do almost exactly the same things. It's simply a choice of syntax.

[raziel_]

eclipsed4utoo is right its just a syntax to write a logic down.

[SixOfEleven]

There is usually never a better or best. In the end it all boils down to personal preference. Some people like the syntax of VB.NET better than C# and the reverse is true as well. I like the syntax of C# better than VB.NET so I'm in the C# camp. If you don't like one then try the other instead.

[MANASWIMEHARKURE]

thnks frnds will learn c# then>>>

[tlhIn`toq]

MANASWIMEHARKURE, on 20 July 2011 - 08:56 PM, said:

ANY IDEA OF TUTORIALS !!!!!!!!!!!
I MEAN BEST BETWEEN VB.NET,C# AND ALL THAT...

One: Switch to decaf. There is no reason to scream, and that is what ALL CAPS is: Screaming. Nor are you going to get a lot more friendly response by holding down the ! keys for 15 of them.

Learn some basic network etiquette ('netiquette') if you plan to use the internet to communicate with people. This link has more detail but the biggies are:

• DON'T SCREAM AT PEOPLE IN ALL CAPS
  
• Don't insist that your needs are vital/important and must be answered immediately. They are only vital to you because you are on deadline and waited so long to ask for help/study your textbook/start your project/learn your coding craft. The people reading the message are volunteers who have a life and do this to give back to the community. Being demanding of them does NOT make them want to help you more and generally has the opposite affect.
  
• Don't use txt/sms/leet/T9 speak like: u no, dn't, wut, coz, b4, and so on. dis not b d'hood dawg... You are sitting at a real keyboard with a real monitor, not a cell phone. You are not here texting your high school posse to come to your kegger after their shift at Taco Bell. You are here asking for help from senior coding professionals who graciously donate their valuable time to helping the next generation of coders with their chosen craft. Please try to show them, yourself and the industry some respect by writing at least at an eighth grade level. (IE: English not ebonics or SMS, real words, punctuation and so on). If you can't take your own problem/question seriously enough to write like an adult, then why would you expect anyone else to take it seriously?
  
• 25 !!!!!!!!!!!!! or ?????????? Don't somehow make your question more important. Refer to the above post and write like a grown up.
  
• Remember your message is being read by real people. Show them some respect. At the same time, remember they are a bunch of strangers that have never met you. So if they offer advice that seems simple to you don't get offended and think they are talking down to you. They don't know you or your skill level. If they are offering you "dumbed down" advice it's because you haven't shown them adequate examples of what you have tried, giving them an example of what your skill levels are.

---

FAQ (Frequently Asked Questions - Updated July 2011

---

Q: My program doesn't work. I didn't show you any code or actually tell you the error message. How do I fix it?
A: What have you tried so far? It is a requirment of this site that you at least make an effort to research (read the MSDN) and code a good faith effort for your own problem. Can you share your current code with us and better explain what issues or errors you are getting? Give us something to go on

Q: How do I get Form 'A' to make a change or talk to Form 'B'
A:

• Passing values between forms/classes
  
• Bulding an application - Part 1
  
• Building an application - Part 2
  
• Quick and easy custom events

Q: I'm trying to make a password/login form and...
A: Password handling tutorial

Q: I'm making a client/server chat program and .....
A: Client/server chat tutorial

Q: I do x and y happens which I didn't expect but I don't know how to figure out why. How do I debug and find my problem?
A:

• Debugging tutorial
  
• Debugging tips
  
• Debugging in detail
  
• Great debugging tips
  
• It still doesn't work, article

Q: I don't understand XML Serialization so I can save my information/class
A:

• Separating data from GUI - PLUS - serializing the data to XML
  
• XML Serialization thread

Q: How do I get sound in my program?
A: Adding sound to your C# application

Q: How do I use the serial port?
A: Serial port communication

Q: How do I deploy my program / Make an installer?
A: C# application deployment project

Q: How do I do compression or .zip files?
A:

• (de)Compression tutorial
  
• Zip files tutorial

Q: How do I do multi-threading? Having a problem with cross-threading...
A:

• Cross thread calls tutorial
  
• How to use a thread pool.
  
• thread synchonization
  
• Advanced threading
  
• MSDN asynch communication

Q: I am making a calculator as my school homework project and ...
A: Calculator tutorial

Q: I've been struggling with this for days/weeks and I can't figure it out and my professor is worthless and can't teach. Can someone here explain it to me?
A: If you are struggling with how to do this you need to talk to your professor. Let him/her know you are struggling at this early stage in class. Make your professor do the job (s)he gets paid to do by either helping you or finding you a tutor or giving you more exercises from earlier in the book. You are paying for this education. Be an active part in not allowing the teacher to brush you off and let you slip through the cracks. If the other 50 people in class aren't struggling then don't blame the teacher. If the other 50 people are struggling then you all need to go to the professor's superior and tell him/her. If the prof is really incompetent then you don't need to help him keep his cushy 100,000/year job. If the prof isn't incompetent then you need to study harder or consider buying another book on programming. You aren't require to ONLY use the text book provided for the class.
"How do you resolve your issues" survey.

Q: How do I save some information like preferences, settings or other data?
A:

• Separating data from GUI - PLUS - serializing the data to XML
  
• Working with environmental variables
  
• Writing a text file tutorial.
  
• Reading a text file tutorial.

Q: I want my textbox to offer suggestions as someone types.
A: Creating an auto-complete textbox

Q: I want to write a program that does x, y and z with features for A, B, and C.
A: {Notice there is no question in this question} That is a very good statement of intent. Go right ahead. You don't need to announce your intentions to us, nor get anyone's permission.
After you have made an effort to your own code (in good faith as described in the Welcome DIC email you got when you joined) and the forum rules that I'm sure you read before posting, and you have a QUESTION about this project... Please post the QUESTION here in this same thread. There is no need to start a new thread for this same topic.

Q: I need to code to do x... Someone tell me the code for y...
A: Your question is about to get bounced for begging for code anyway but...
So you're asking the volunteers here to write your code for you, to make it do everything in your wish list? Please read the rules. You seem to misunderstand what we do here. We help people learn to code. We help people with their projects. We help people better understand the errors and exceptions they are getting so they can fix their issues. We are not a free code writing service. If you have made an effort to code a specific feature, but are not getting the results you wanted then please post the relivant code for that feature along with the error messages or an explanation of what results you are seeing as compared to the results you were expecting, and we will try to guide you onto the right path.

Q: What is the best programming language? What programming language should I learn?
A: All of them. And none of them. You might as well be asking "What is the best kind of vehicle?" Because the answer for both questions is "It depends on your needs and what personally suites you the best." C, C++, C#, Objective-C, Cocoa, F#, Visual Basic, Python, JAVA... Are all good languages. They all have their pros and cons. They each have their strengths and weaknesses. Some have stronger footholds in some markets than others. Do you want to write for iPhone/iPad then you need Objective-C. Do you want to write for generic mobile phone use then you need JAVA. And so on. If you have no idea what area of programming you want to move to (Gaming, Financial, Windows, Macintosh, Cell phones) then nobody can advise you on a language. Personally, I would point you to C# because, like it or not, Microsoft owns the desktop computer market and C# will teach you good habits of design, OOP (Object Oriented Programming) design, inheritance and so on: Concepts that translate well to all other OOP languages.

Q: How do I get my program to programmatically simulate a mouse click or button press?
A: Simulate mouse and keystroke (even to another application)

Q: I'm not really sure what I want to do with my future? Do you guys like programming? I think I kinda like math and games and computers? What should I do or study?
A: Get experience while you find yourself

Q: What books should I buy? What tutorials should I do? Where should I start to learn programming?
A:

---

Standard resources, references and suggestions for new programmers. - Updated July 2011

---

Don't try to create a useful working program to fit a need of yours (or a for-pay contract) as your introduction to coding project. When you are learning to code you don't know enough to code a program, let alone know how to engineer the architecture of a program. It would be like saying "I don't know how to read sheet music, or play an instrument. I think I'll write a 3 act opera as my first learning experience."

The problem with taking on large, complex tasks when you are new to coding is that

• It will frustrate you to the point of quitting. We don't want you to quit. We want you to succeed and learning how to code and engineer software.
  
• You don't know enough about coding to know where to start or in what direction to design your program
  
• You risk learning via the 'Swiss cheese' method where you only learn certain bits and pieces for the one project but have huge holes in your education.

Finding answers to specific problems:
Sometimes just knowing where to look can make all the difference. Google is your friend.
Search with either "C#" or "MSDN" as the first word: "MSDN Picturebox", "C# Custom Events", "MSDN timer" etc.
How to do a good search that will get you targeted answers.

Don't think you are the first person to ask a question. Try a search on this site to see if someone has already brought up this problem. Also, as soon as you post your question go to the bottom of the updated page: You will see where the system has already analyzed your question and tried to find similar threads for the same question, so check those links out.

But honestly, just typing away and seeing what pops up in Intellisense is going to make your self-education take 20 years. You can learn by trying to reverse engineer the language through banging on the keyboard experimentation - or you can learn by doing the tutorials and following a good "How to learn C#" book. There are so many great "How do I build my first application" tutorials on the web... There are dozens of "Learn C# in 21 days", "My first C# program" type books at your local book seller or even public library.

Beginner:
Build a Program Now! in Visual C# by Microsoft Press, ISBN 0-7356-2542-5
is a terrific book that has you build a Windows Forms application, a WPF app, a database application, your own web browser.

Visual Studio Keyboard Shortcuts


D.I.C. C# Resource page Start here
Intro to C# online tutorial then here...
C# control structures then here.
MSDN Beginner Developer video series
MSDN video on OOP principals, making classes, constructors, accessors and method overloading
MSDN Top guideline violations, know what to avoid before you do it.
Design patterns as diagrams

I hate sending people to another site when we have such good tutorials here, but this series shouldn't be overlooked.
Programming OOP in C# - Part 1
Programming OOP in C# - Part 2
Programming OOP in C# - Part 3
Programming OOP in C# - Part 4
Programming OOP in C# - Part 5

Writing a text file is always one of the first things people want to do, in order to store data like high-scores, preferences and so on
Writing a text file tutorial.
Reading a text file tutorial.

Have you seen the 500+ MSDN Code Samples? They spent a lot of time creating samples and demos. It seems a shame to not use them.

Intermediate:
The tutorials below walk through making an application including inheritance, custom events and custom controls, object serialization and more.
Bulding an application - Part 1
Building an application - Part 2
Quick and easy custom events
Separating data from GUI - PLUS - serializing the data to XML
Passing values between forms/classes

Working with environmental variables
'Why do we use delegates?' thread

And everyone always wants to connect to a database, right out of the gate so
Database tutorials right here on DIC

C# Cookbooks
Are a great place to get good code, broken down by need, written by coding professionals. You can use the code as-is, but take the time to actually study it. These professionals write in a certain style for a reason developed by years of experience and heartache.

Everyone:
Debugging tutorial
Debugging tips
Debugging in detail
Great debugging tips
It still doesn't work, article

Microsoft Visual Studio Tips, 251 ways to improve your productivity, Microsoft press, ISBN 0-7356-2640-5
Has many, many great, real-world tips that I use all the time.

These are just good every-day references to put in your bookmarks.
MSDN C# Developers Center with tutorials
Welcome to Visual Studio
Free editions of Visual Studio 2010

Let me also throw in a couple tips:

• You have to program as if everything breaks, nothing works, the cyberworld is not perfect, the attached hardware is flakey, the network is slow and unreliable, the harddrive is about to fail, every method will return an error and every user will do their best to break your software. Confirm everything. Range check every value. Make no assumptions or presumptions.
  
  
• Take the extra 3 seconds to rename your controls each time you drag them onto a form. The default names of button1, button2... button54 aren't very helpful. If you rename them right away to something like btnOk, btnCancel, btnSend etc. it helps tremendously when you make the methods for them because they are named after the button by the designer.
  btnSend_Click(object sender, eventargs e) is a lot easier to maintain than button1_click(object sender, eventargs e)
  
  
• You aren't paying for variable names by the byte. So instead of variables names of a, b, c go ahead and use meaningful names like Index, TimeOut, Row, Column and so on. You should avoid 'T' for the timer. Amongst other things 'T' is commonly used throughout C# for Type and this will lead to problems. There are naming guidelines you should follow so your code confirms to industry standards. It makes life much easier on everyone around you, including those of us here to help. If you start using the standards from the beginning you don't have to retrain yourself later.
  
  
• Learn how to search the 'net for examples. How to do a good search that will get you targeted answers.
  
  
• Try to avoid having work actually take place in GUI control event handlers. It is usually better to have the GUI handler call other methods so those methods can be reused and make the code more readible.
  

  btnSave(object sender, eventargs e)
  {
      SavePreferences();
  }
  
  SaveMenuItem(object sender, eventargs e)
  {
      SavePreferences();
  }
  
  SaveContextMenu(object sender, eventargs e)
  {
      SavePreferences();
  }
  
  Form1_Closing(object sender, eventargs e)
  {
      if (IsDirty) SavePreferences();
  }
  

  
  
  
• This can't be stressed enough in today's world of cell phone messaging:
  Don't use txt/sms/leet/T9 speak like: u no, dn't, wut, coz, b4, and so on.
  dis not b d'hood dawg... You are sitting at a real keyboard with a real monitor, not a cell phone. You are not here texting your high school posse to come to your kegger after their shift at Taco Bell. You are here asking for help from senior coding professionals who graciously donate their valuable time to helping the next generation of coders with their chosen craft. Please try to show them, yourself and the industry some respect by writing at least at an eighth grade level. (IE: English not ebonics or SMS, real words, punctuation and so on). If you can't take your own problem/question seriously enough to write like an adult, then why would you expect anyone else to take it seriously?
  
  
• I strongly suggest installing VMware or some other virtualization technology on your development PC so you can create a couple virtual computers for testing. This would allow you to debug and test inside: WinXP32, XP64, Vista, Win7x32, Win7x64... etc. without having to actually have 5 physical PC's. Visual Studio will let you send the debug directly into one of these virtual machines so you can watch it operate, check its variables, see the crashes and so on just as if it were debugging on your real machine.

This post has been edited by tlhIn`toq: 21 July 2011 - 10:04 AM

[bdemorrow]

MANASWIMEHARKURE, on 20 July 2011 - 07:56 PM, said:

ANY IDEA OF TUTORIALS !!!!!!!!!!!
I MEAN BEST BETWEEN VB.NET,C# AND ALL THAT...

The fact of the matter is that it's an opinion that you'll have to earn yourself.
My personal opinion is that C# is easier to read and interpret at a glance (and offers some keywords not available in VB .NET such as 'yield').

You may also be interested to know that several of the large projects that I've seen have chosen C# over VB - such as Mono SVN.

Bottom line, try them both and make your own decision. I personally prefer C#.

[???]

Microsoft Intermediate Language (MSIL).

[Psyguy]

When I transitioned from college, where I was using C++, to the workforce, where they were using VB.NET, I asked the same question (Why vb.net over c#?). The real answer is, it doesn't matter which you learn because you should be able to transition to the other if the need arises. Personally, I could go from the VB version to the C version in less than a week. I assume the same would be true for anyone who wanted to do so who is familiar with the framework.

Right now, VB.NET is easier for me because I am working with it every day, but I wouldn't say either is better. The fan-boys will always tell you their chosen style is better. In the end, you just have to make a choice and learn it.

The one thing I WILL say that C# has over VB.NET is that when you get stuck (and you will) there are a lot more resources available for the C based style. That being said, you can still use them, but you will have to convert the syntax into VB. I haven't ran into an example written in C# yet that I couldn't translate into VB.NET.

[CodingSup3rnatur@l-360]

Quote

..and offers some keywords not available in VB .NET such as 'yield').

The iterator pattern through the use of yield is actually now supported in VB.NET (about time too I think!) as part of the new async pattern download - Here. (The new task based asynchronous pattern is crazy awesome by the way!)

I personally recommend C# though, of course. VB.NET's syntax doesn't agree with me

This post has been edited by CodingSup3rnatur@l-360: 23 August 2011 - 12:30 PM