Now that we know what term means what, we can look at different versions available
of each. The subject of the version numbers chosen by Microsoft and what??™s in
which version is a slightly convoluted one, but it??™s important that we all agree on what
we mean when we talk about a particular version.
1.3.2 Untangling version number chaos
A newcomer to the industry might think that coming up with version numbers would
be easy. You start with 1, then move on to 2, then 3 in a logical progression, right? If only
that were the case??¦ Software products and projects of all natures like to keep minor
version changes distinct from major ones, and then there are patch levels, service packs,
build numbers, and so forth. In addition, there are the codenames, which are widely used
and then abandoned, much to the frustration of ???bleeding edge??? book authors and
publishers. Fortunately from the point of view of C# as a language we can make life reasonably
straightforward.
NOTE Keeping it simple: C# 1, C# 2, and C# 3??”Throughout this book, I??™ll refer to
C# versions as just 1, 2, and 3. There??™s little point in distinguishing
between the two 1.x versions, and no point in adding a cumbersome
extra ???.0??? every time I refer to the different versions??”which of course I??™ll
be doing quite a lot.
We don??™t just need to keep track of the language, unfortunately.
Pages:
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85