This is hard enough in Windows, let alone you venture out to other platforms! Extending the system is not what a typical application does, hence it's not part of the framework. You'd need to write a Shell Extension[^], which has become a bit harder since the introduction of 64-bit machines.
1. Do any of you have tips regarding what I need to remember and what I can simply pull up from Visual Studio?
What's "pull up"? Usually the answer is "when I press '.'", which should be Ctrl-Space. Intellisense shows the available types in the currently loaded namespaces, as available in the currently referenced assemblies. Most members of those types are available, along with any XML-documentation and a reflection of the parameters, and and indication of any overloads.
Maurice Lantier wrote:
2. Do any of you have suggestions regarding the best way to begin remembering code? 3x5 cards, etc...?
Memorizing isn't going to help, you'll need to experiment. A lot.
No, I really mean a lot!
Maurice Lantier wrote:
3. Any suggestions regarding websites to access, good video's, etc... to help with my learning the necessary?
This site, MSDN and Coding4Fun would be my top three; problem is, first is a community, not a school; second is a reference-site, not a manual, third is too complex often to use it for starters.
It couldn't have been the Help-file (available under F1). You obviously have internet, so that's your primary resource - CodeProject and MSDN. The first is the ideal starterplace for new projects, the articles provide a nice basis for new applications, and the forums are usually open. The second is the ideal reference, explaining how the building-blocks that are available, look like.
Best recommendation is a good book, not an ebook, but one you can use to kill small animals. Both Manning and O'Reilly offer a nice range of books.
You're welcome, hope that more people respond with something more original
You should remember the places where you need to look, and where common things are. Intellisense is great when you know what you are looking for, but if you don't know the class name it won't help. For example, a C++ or Java person might try looking for 'Map', and the autocomplete will fail them completely – but knowing that you can find collections under System.Collections.Generic will give you the clues you need.
You also need to develop Google-fu. C# is a very popular mainstream language, and most problems you're likely to have have been solved and published already, if you can find them. StackOverflow is a trustworthy site if it appears with an answer for your question (I'll take the downvotes for recommending it, it's better than CP in my opinion for small, self-contained questions), as is CP, and MSDN.
The best way to learn depends on your personal style. Myself, I enjoy learning by example so I would get a tutorial or a book and leave that on my desk (virtual or real), and then try creating some simple applications to pick things up. The Framework is too big to learn it academically and expect to hold onto it.
A large percentage of my code generally comes from the internet simply because it's both a pain and unnecessary to re-write code that someone else has written and tested. The rest is from writing my own code and adjusting the samples I've found online to fit my purpose. Basically, google-fu
As has previously been said, I strongly advise you experiment. A lot. The best advice I can give you is to code, code and code. It's like learning a musical instrument. You only get better with practice. Make simple projects for yourself and write them. As you get better, you'll find yourself designing better code and reusing functions and classes you've written previously and even get to writing your own code library.
A good book always helps, I feel that "Programming C# 4.0" by Jesse Liberty et al. is an essential desktop purchase. Pretty much the core of the language is clearly explained part by part with a simple example to show you it in use. Jon Skeet's "C# in Depth - Second Edition" will help you better understand what is going on in your programs.
Finally, don't be afraid to experiment and ask for help if you get stuck. We all began somewhere and the majority of people will be keen to help if they can.
Last Visit: 31-Dec-99 19:00 Last Update: 24-Dec-14 15:18