Talk:Visual Basic (.NET)
This is the talk page for discussing improvements to the Visual Basic (.NET) article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1 |
This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||||||
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
Please add the quality rating to the {{WikiProject banner shell}} template instead of this project banner. See WP:PIQA for details.
|
Nominative link
In the infobox on the right there is a link to nominative coding, but on that page there isn't the anchor the link is referring to. —Preceding unsigned comment added by 62.45.201.255 (talk) 18:51, 11 November 2009 (UTC)
- Fixed. Changed link to Nominative type system. -- Tom N (tcncv) talk/contrib 01:15, 12 November 2009 (UTC)
Comparisons between VB.NET to VB6 are outdated
The article has a large part comparing VB.Net to VB 6. I think that should all be removed apart from may be a small reference to the origin of BASIC itself. Nobody would consider "upgrading" a VB 6 project (after being amazed that they still exist) to a .Net version without completely rewriting it as the languages are further apart than the difference between a T-Ford and a Ford Mondeo. At the start of the ".Net-era", programmers might have been interested in the differences between the new language and the one they were using, but now a rewrite of a VB 6 project resembles rewriting a COBOL project.
If any comparison should be made, it should of course be to C#. I hate C# because it shows it was meant to be shorthand for assembly and by now combines that with LINQ. I'm not the one who should change this article, but someone should. Joepnl (talk) —Preceding undated comment added 00:30, 6 July 2011 (UTC).
Rename
The .NET suffix has not been used for a long time. The language is simply called "Visual Basic" nowadays, not "VB.NET". 86.150.195.140 (talk) 15:12, 13 July 2012 (UTC)
- I agree totally. Even on MSDN, the language is referred to as Visual Basic, not Visual Basic.NET. JoeWang4 (talk) 21:47, 18 January 2013 (UTC)
- Hi. There is already a Visual Basic article. What are we supposed to do with that? Best regards, Codename Lisa (talk) 01:25, 19 January 2013 (UTC)
- Most people seem to refer to it as Classic VB but its not a name which sits well with me. Particularly since there are still other venders of Visual Basic. Its just that Microsoft is the most popular.SaintGerbil (talk) 12:29, 21 August 2013 (UTC)
- The above, if correct, means THIS article is WRONG. I don't understand WHY it has been allowed to stand for so long. In addition, the article on Visual Basic is also WRONG. To give the OBVIOUS answer to the question "what do we call the other article?", we call it Visual Basic 6.0 (and its predecessors). VB6 is 16 years old and is a curiosity for the vast majority of coders - just like Fortran or Cobol. Visual Basic is Microsoft's adaptation of BASIC to handle the GUI/mouse programming for simple Windows programs in the early 1990's. With the introduction of Windows 3.0, Microsoft finally had a fairly robust entry into GUI Operating Systems and providing entry-level programmers the ability to code with Windows reinforced the different business model compared to Apple's insular vertically integrated approach. I view VB6.0 as an ancestor, or earlier version, of what VB is today. Clearly to be consistent with reality, the MAIN article on VB should be about the CURRENT version and shouldn't be qualified as .NET specific. — Preceding unsigned comment added by 216.96.77.81 (talk) 16:38, 8 November 2014 (UTC)
- Hi. You didn't answer my question: Supposing that you are right, what exactly are we supposed to do now? Best regards, Codename Lisa (talk) 10:19, 9 November 2014 (UTC)
- How about merging the current "Visual Basic" one into the History subsection of this one? And then either renaming this one "Visual Basic" or leaving the name and redirecting the name "Visual Basic" into the History subsection. Eykeklos Omnia (talk) 21:35, 28 November 2019 (UTC)
- Hi. You didn't answer my question: Supposing that you are right, what exactly are we supposed to do now? Best regards, Codename Lisa (talk) 10:19, 9 November 2014 (UTC)
- Hi. There is already a Visual Basic article. What are we supposed to do with that? Best regards, Codename Lisa (talk) 01:25, 19 January 2013 (UTC)
Outdated - 2012
Visual Studio 2012 has been released--time to update? kazu (talk) 09:10, 2 October 2012 (UTC)
Hungarian Notation
From the article: "The 'cmd' prefix is replaced by the 'btn' prefix, conforming to the new convention previously mentioned."
Hungarian notation is discouraged by Microsoft
Rather than get into what we should and should not be doing with standard why not follow the other examples and use the default values i.e. "Button1" rather than btnClose.
It avoids new developers starting bad habits and avoids the issues around standards. SaintGerbil (talk) 12:27, 21 August 2013 (UTC)
Old IDE desktop icon at top of article
Keeping the desktop icon of some obsolete IDE at the top of the infobox for a language article is totally arbitrary. It is not an official logo of the VB.NET language, nor is it related to the image below. Not a single article for any other programming language has this. It is like putting an old NetBeans IDE desktop icon at the top of the Java article, or a C# Express 2008 desktop icon at the top of the C# article. Karpouzi (talk) 06:48, 13 May 2014 (UTC)
- Hi.
- Thanks for the explanation, though I am not sure how I was supposed to get all this from your edit summary, "vb express stopped in 2010". I don't understand what you mean by "official": Microsoft has created this and put it in the corresponding product, hence it is official. If it is outdated, it should be updated, not removed; an old logo is better than no logo. On the other hand, if you are suspected of forgery (hence your "official" comment), we can request the uploaders – RJKings (talk), FleetCommand (talk), Arjun G. Menon (talk) – to join in.
- And if you haven't seen logos in any other article, well, here is a couple of links to get you started with "seeing": Visual C++, Visual C#, F#, Axum, Oxygene.
- Best regards,
Codename Lisa (talk) 09:41, 13 May 2014 (UTC)
- You are confusing the logo of a programming language with the desktop icon of an IDE. I think I clearly stated which I was referring to. The infoboxes for F#, Axum, Oxygene, Java, Ruby, Python and almost all the others have "logo = " displaying the official logo taken from the website, not an icon from an IDE. Karpouzi (talk) 08:57, 15 May 2014 (UTC)
- Unless you are implying that IDE is an unreliable source, I don't see how it can be anything beyond a technical difference. VB.NET, C# and VC are developed by Microsoft, hence their nature corresponds to the commercial focus of Microsoft. That Microsoft has recently shifted its language-oriented focus to a platform and purpose-oriented one does not make these logos unofficial. They are still Microsoft's. And most importantly, I don't know why you switched from age discussion to origin discussion. So, feel free to obtain their replacement from either website or IDE. I don't mind. Unless, of course, there is something you haven't said.
- Best regards,
- Codename Lisa (talk) 13:13, 15 May 2014 (UTC)
Syntax
This article is just a stub, right? WHY is Syntax the first section after the lede? Using the C++ article as a template, its first section is "History". Its obvious that spending a bit of time on (historical) context is NECESSARY for any good encyclopedia article, isn't it? Isn't it also obvious that this should come sooner rather than later? I also have some concrete suggestions to expand the contents of the section:
1."Groups of statements are terminated with keywords such as "End If", or "End Sub", instead of using braces. Braces are also known as curly brackets "{}"s and are the convention used by languages such as C and C++."
This is terrible. Let me give you an example:
Dim a As Long
If TRUE Then
a = 1+1/3
End If
So, what is the "group" of statements which "End If" terminates? Specifically, are we claiming that "If True Then" is a statement?!? We are certainly implying that the Dim statement, as part of the "group", needs a keyword to be terminated, right? Also, please explain to me how the (implicit) Namespace is (explicitly) terminated when writing code? It is not. This statement ONLY makes sense to those programmers who understand what a compound statement is. How useful is this? In C & C++, I can toss { and } around a bunch of statements and create a block or compound statement, there IS no equivalent in VB. VB has single (logical) line statements which are "terminated" by the end-of-line (new line) (eg. Dim A As Integer)(eg. A = A + 3) OR compound statements ( or enclosing language structures such as Class, Module, Function, Namespace) which begin with a line containing a keyword (possibly preceded by modifiers) and are terminated with a line with another keyword. For...Next; If...Then...End If; Class...End Class are examples of compound statements. In C++ the end of a line of code has no importance and is generally ignored.
2."Statements are terminated with a new line, instead of semicolons - the convention used by languages such as Pascal and C." See above. It is just NOT TRUE. eg If Then End If is NOT terminated by a end-of-line.
3."Variables are both assigned and compared using an equals sign." How about: The "=" symbol is used to both assign and to compare.
(compare this to Pascal use of := to assign and = to compare, or to C which assigns with = and compares with ==).
4."Round Brackets are used with arrays, both to declare them and to get a value at a given index in one of them, as compared to languages such as C which use Square Brackets for array declaration and access." This is NOT the only use of ( and ) and is such a minor point that it does NOT BELONG HERE, imho. Perhaps in a table comparing various language features in C, C++, BASIC, Pascal,...?
5. Comments are single line and are started with the single quote character '. Replace with: "Comments must occupy an entire line, and begin with a single quote character, '. This means that comments can NOT added to a line of code. Most other modern languages allow insertion of comments on the line they are applicable to, which can make the code easier to follow. Also, multiline comments must have each line begun with a '. This doesn't allow blocks of code to be quickly "commented out" (and so ignored by compiler) which can be a great aid to debugging. — Preceding unsigned comment added by 216.96.77.81 (talk) 18:02, 8 November 2014 (UTC)
Syntax comparisons in article (VB6, C# etc)
According to your revert argument, you must also remove the entire section comparing VB.NET and VB6 syntax. WP:SS allows for a summary section in the main article, and the comparison is basic and short.
Also, there is exactly zero unnecessary syntax in the C# examples, which were based on the official documentation from Microsoft below. If there is, then feel free to modify it, instead of deleting the whole thing.
https://msdn.microsoft.com/en-us/library/06tc147t.aspx https://msdn.microsoft.com/en-us/library/5011f09h.aspx
Karpouzi (talk) 12:06, 14 February 2015 (UTC)
- Hi.
- Please don't put word in my mouth; I feel no obligation too keep an extremely low quality example just because a high quality one exists; nor do I feel the obligation to delete a high-quality example just because a low quality one is deleted.
- Violating a founding policy such as WP:NPOV is unacceptable, be it by you or by Microsoft documentations. C# and VB.NET have important differences like Ternary operators.
- Best regards,
- Codename Lisa (talk) 02:03, 15 February 2015 (UTC)
Move to "Visual Basic" as per WP:COMMONNAME
Requested move 25 April 2021
It has been proposed in this section that multiple pages be renamed and moved. A bot will list this discussion on the requested moves current discussions subpage within an hour of this tag being placed. The discussion may be closed 7 days after being opened, if consensus has been reached (see the closing instructions). Please base arguments on article title policy, and keep discussion succinct and civil. Please use {{subst:requested move}} . Do not use {{requested move/dated}} directly. |
– As per WP:COMMONNAME, when people say "programming in Visual Basic" today, they are most likely referring to Visual Basic .NET, not VB6. Microsoft's official website simply calls it "Visual Basic". Félix An (talk) 18:09, 25 April 2021 (UTC) Félix An (talk) 18:09, 25 April 2021 (UTC)
- Referring to Visual Basic 6 as classic Visual Basic without providing reliable sources demonstrating that it is indeed the common name is simply using Wikipedia to make up facts. Start by providing the sources. TEDickey (talk) 19:53, 25 April 2021 (UTC)
- We can call it Visual Basic (legacy) or something like that. Félix An (talk) 22:27, 25 April 2021 (UTC)
- What do you think would be a suitable name to refer to VB6? I could use some help finding some reliable sources to find a good name to describe VB6. Félix An (talk) 22:28, 25 April 2021 (UTC)
- We can call it Visual Basic (legacy) or something like that. Félix An (talk) 22:27, 25 April 2021 (UTC)
- (Request at Talk:Visual Basic merged into this one) – Thjarkur (talk) 21:29, 25 April 2021 (UTC)
- The current topic covers Visual Basic 5 and 6 (so renaming it to "Visual Basic 6" wouldn't work well). But looking to see what's a suitable common-name involves more than a talk-page discussion (talk pages are never reliable sources, but are places to discuss sources TEDickey (talk) 23:26, 25 April 2021 (UTC)
- All unassessed articles
- C-Class Computing articles
- Mid-importance Computing articles
- C-Class software articles
- Mid-importance software articles
- C-Class software articles of Mid-importance
- All Software articles
- All Computing articles
- C-Class Microsoft articles
- Mid-importance Microsoft articles
- C-Class .NET articles
- High-importance .NET articles
- WikiProject .NET articles
- WikiProject Microsoft articles
- Requested moves