|
You are correct. However, the books at least have to go through publishing whereas online tutorials are often copy and pasted outright theft of others work with no real knowledge by the other. Or worse, in online tutorials, the Author usually starts with an overly complex example to demonstrate a trivial task.
|
|
|
|
|
I also recommend starting with a book. But I found that it wasn't enough for me so I took a course and it made a lot of difference. The ability to speak with and get feedback from someone who knows the subject can be quite valuable.
At the moment I find myself having to learn [the .net language that shall not be named] so I will likely buy a book today.
|
|
|
|
|
I recommend Option Strict On as the very first line.
|
|
|
|
|
I shall endeavor to check that that is in their coding standards... if they have any. 
|
|
|
|
|
I added it to my vbc.rsp file -- putting it in every file is just silly.
|
|
|
|
|
that turns you into an advanced VB jockey.
|
|
|
|
|
If it's worth doing (it isn't), it's worth doing right.
|
|
|
|
|
I agree.
|
|
|
|
|
Only three things you need to know,
1) Option Explicit
2) AndElse, AndOr (OMFG)
|
|
|
|
|
When I was looking at a list of differences between the langauges on Wikipedia yesterday I noticed that they have IsNot; I want that in C#.
|
|
|
|
|
object1.ReferenceEquals(object2)
Edit, shows how much I use it. should be
Object.ReferenceEquals(object1, object2);
|
|
|
|
|
|
T M Gray wrote: Once you have a grasp on the basics
In my opinion, neither ASP.net nor WinForms is "the basics" -- new developers should learn "the basics" of the language before attempting ASP.net and WinForms.
|
|
|
|
|
That is a very purist point of view. For many people if they don't apply what they learn to real situations they won't absorb it as well. And to me, you don't really know the basics if you can't produce something useful. If I say I have a basic knowledge of chess I would be implying I could actually play a game start to finish. Using your definition of the basics it would only imply I could identiy the pieces.
|
|
|
|
|
T M Gray wrote: That is a very purist point of view
Of course.
The programs that were assigned when I first learned to program are not applicable to real situations -- they teach the fundamentals.
It's the same way they teach sports -- learn each part separately, then show how to put the pieces together to play a game.
T M Gray wrote: produce something useful
Even when I was just learning I took it upon myself to write programs I found useful using the techniques that had been covered to that point.
T M Gray wrote: I could identiy the pieces
I seem to recall reading about a chess teacher who teaches kids one piece at a time -- some exercises that teach just how knights move, just how rooks move, etc. and how they can be used together. And only after the students have become familiar with each of the pieces, starts to mix the pieces together.
A better, more structured, teaching technique is more likely to produce better practitioners.
It seems there are a lot of "developers" here who learned the easy way and never learned the intricacies of for loops -- their educations are stunted by not getting the fundamentals the way we old dogs did.
|
|
|
|
|
I watched several SQL related LearnVisualStudio videos a couple of years back and found them to be somewhat useful.
If you're looking for an introductory general purpose programming course, I highly recommend this[^] one @ MIT OpenCourseware. I'm also a huge fan of Stanford Engineering Everywhere[^] and am currently wading thru their course on Machine Learning[^]. Btw, SEE also has a great "Programming 101" course that features the venerable Karel (the Robot).
/ravi
|
|
|
|
|
Hi Ravi
Just had a look at the SEE courses at Standford and they look like something that is useful for me. These courses in combination with some good textbooks is probably what I would go for. Thank you very much for the valuable links.
/Eiel.
|
|
|
|
|
I'm going through the MIT material (I just watched video 7) -- it is very good. Thanks for pointing it out.
|
|
|
|
|
Glad you like it - I think it's a great set of videos regardless of one's experience!
/ravi
|
|
|
|
|
In AssemblyInfo.cs
1. What is the difference between AssemblyVersion and AssemblyFileVersion? Why would you specify different values for the two different attributes?
2. More importantly, I see the following comment in my AssemblyInfo.cs file:
This sounds like a neat idea so I thought I'd try it. But, when I access the version info in my app at runtime, using Application.ProductVersion, it still only returns the string "1.0.*". What am I doing wrong here?
|
|
|
|
|
|
If it's your application, they mean what you want them to mean.
|
|
|
|
|
|
hi!
i have an ini files. in this file, the value is in following format:
abc= mno
xyz=ijk
efg=pqr
and so on.....
my need is that i have to store the value before= (abc,xyz) in an array and after=(mno,ijk) in another array.
and after storing the value in an array, replace abc with mno and so on in C#
|
|
|
|
|
And what part of this is giving you a problem?
And why are you using .INI files anyway - they pretty much went out with Win98!
Did you know:
That by counting the rings on a tree trunk, you can tell how many other trees it has slept with.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
