imported>IndependentCharm83: Added links to other articles, minor grammar fixes and editing, and added a fact about being able to reference VB code from C# and vice versa

2025-10-04T10:19:22Z

Added links to other articles, minor grammar fixes and editing, and added a fact about being able to reference VB code from C# and vice versa

← Previous revision		Revision as of 10:19, 4 October 2025
Line 21:		Line 21:
	\| platform = [[.NET Framework]], [[Mono (software)\|Mono]], [[.NET]]<ref>{{cite web\|url=https://blogs.msdn.microsoft.com/vbteam/2018/11/12/visual-basic-in-net-core-3-0/\|title=Visual Basic in .NET Core 3.0\|first=Kathleen\|last=Dollard\|website=blogs.msdn.microsoft.com\|date=November 13, 2018\|access-date=November 21, 2018\|archive-date=November 19, 2018\|archive-url=https://web.archive.org/web/20181119070011/https://blogs.msdn.microsoft.com/vbteam/2018/11/12/visual-basic-in-net-core-3-0/\|url-status=live}}</ref><ref name="devblogs-2020-03-11">{{cite web \|url=https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/ \|title=Visual Basic support planned for .NET 5.0 \| Visual Basic Blog \|publisher=Blogs.msdn.microsoft.com \|date=2020-03-11 \|access-date=2020-08-26 \|archive-date=January 5, 2022 \|archive-url=https://web.archive.org/web/20220105022953/https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/ \|url-status=live }}</ref>		\| platform = [[.NET Framework]], [[Mono (software)\|Mono]], [[.NET]]<ref>{{cite web\|url=https://blogs.msdn.microsoft.com/vbteam/2018/11/12/visual-basic-in-net-core-3-0/\|title=Visual Basic in .NET Core 3.0\|first=Kathleen\|last=Dollard\|website=blogs.msdn.microsoft.com\|date=November 13, 2018\|access-date=November 21, 2018\|archive-date=November 19, 2018\|archive-url=https://web.archive.org/web/20181119070011/https://blogs.msdn.microsoft.com/vbteam/2018/11/12/visual-basic-in-net-core-3-0/\|url-status=live}}</ref><ref name="devblogs-2020-03-11">{{cite web \|url=https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/ \|title=Visual Basic support planned for .NET 5.0 \| Visual Basic Blog \|publisher=Blogs.msdn.microsoft.com \|date=2020-03-11 \|access-date=2020-08-26 \|archive-date=January 5, 2022 \|archive-url=https://web.archive.org/web/20220105022953/https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/ \|url-status=live }}</ref>
	\| operating_system = Chiefly [[Windows]]<br/>Also on [[Android (operating system)\|Android]], [[BSD]], [[iOS (Apple)\|iOS]], [[Linux]], [[macOS]], [[Solaris (operating system)\|Solaris]], and [[Unix]] <!-- Mono implementations, remember? -->		\| operating_system = Chiefly [[Windows]]<br/>Also on [[Android (operating system)\|Android]], [[BSD]], [[iOS (Apple)\|iOS]], [[Linux]], [[macOS]], [[Solaris (operating system)\|Solaris]], and [[Unix]] <!-- Mono implementations, remember? -->
	\| license = [[Roslyn (compiler)\|Roslyn]] compiler: [[MIT License]]<ref>{{Cite web\|url=https://github.com/dotnet/roslyn/blob/0d04884c243978cdd609e219fdb63cb58ebec69d/License.txt\|title=Dotnet/Roslyn\|website=[[GitHub]]\|date=November 26, 2024}}</ref~~><br/~~>		\| license = [[Roslyn (compiler)\|Roslyn]] compiler: [[MIT License]]<ref>{{Cite web\|url=https://github.com/dotnet/roslyn/blob/0d04884c243978cdd609e219fdb63cb58ebec69d/License.txt\|title=Dotnet/Roslyn\|website=[[GitHub]]\|date=November 26, 2024}}</ref>
	\| website = {{URL\|https://docs.microsoft.com/dotnet/visual-basic/}}		\| website = {{URL\|https://docs.microsoft.com/dotnet/visual-basic/}}
	\| file_ext = <code>.vb</code>		\| file_ext = <code>.vb</code>
Line 36:		Line 36:
	The Windows Forms library is most commonly used to create GUI interfaces in Visual Basic. All visual elements in the Windows Forms class library derive from the Control class. This provides the minimal functionality of a user interface element such as location, size, color, font, text, as well as common events like click and drag/drop. The Control class also has docking support to let a control rearrange its position under its parent.		The Windows Forms library is most commonly used to create GUI interfaces in Visual Basic. All visual elements in the Windows Forms class library derive from the Control class. This provides the minimal functionality of a user interface element such as location, size, color, font, text, as well as common events like click and drag/drop. The Control class also has docking support to let a control rearrange its position under its parent.

	Forms are typically designed in the [[Visual Studio]] [[Integrated development environment\|IDE]]. In Visual Studio, forms are created using [[drag-and-drop]] techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have [[Attribute (computing)\|attributes]] and [[event handler]]s associated with them. Default values are provided when the control is created, but may be changed by the ~~programmer~~. Many attribute values can be modified during run time based on user actions or changes in the environment, providing a dynamic application. For example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted.		Forms are typically designed in the [[Visual Studio]] [[Integrated development environment\|IDE]]. In Visual Studio, forms are created using [[drag-and-drop]] techniques. A tool is used to place controls (e.g., text boxes, buttons, etc.) on the form (window). Controls have [[Attribute (computing)\|attributes]] and [[event handler]]s associated with them. Default values are provided when the control is created, but may be changed in the Visual Studio IDE GUI or in code. Many attribute values can be modified during run time by code such as based on user actions, or changes in the environment, providing a dynamic application. For example, code can be inserted into the form resize event handler to reposition a control so that it remains centered on the form, expands to fill up the form, etc. By inserting code into the event handler for a keypress in a text box, the program can automatically translate the case of the text being entered, or even prevent certain characters from being inserted.

	== Syntax ==		== Syntax ==
Line 43:		Line 43:

	In addition, in Visual Basic:		In addition, in Visual Basic:
	* There is no unified way of defining blocks of statements. Instead, certain keywords, such as "If … Then" or "Sub" are interpreted as starters of sub-blocks of code and have matching termination keywords such as "End If" or "End Sub".		* There is no unified way of defining blocks of statements. Instead, certain keywords, such as "If ... Then" or "Sub" are interpreted as starters of sub-blocks of code and have matching termination keywords such as "End If" or "End Sub".
	* Statements are terminated either with a [[Colon (punctuation)\|colon]] (":") or with the [[end of line]]. Multiple-line statements in Visual Basic are enabled with " _" at the end of each such line. The need for the underscore continuation character was largely removed in version 10 and later versions.<ref>{{cite web \|url=https://msdn.microsoft.com/en-us/library/ff637436.aspx \|title=New Features in Visual Basic 10 \|date=June 3, 2010 \|access-date=September 5, 2015 \|archive-date=March 4, 2016 \|archive-url=https://web.archive.org/web/20160304231731/https://msdn.microsoft.com/en-us/library/ff637436.aspx \|url-status=live }}</ref>		* Statements are terminated either with a [[Colon (punctuation)\|colon]] (":") or with the [[end of line]]. Multiple-line statements in Visual Basic are enabled with " _" at the end of each such line. The need for the underscore continuation character was largely removed in version 10 and later versions.<ref>{{cite web \|url=https://msdn.microsoft.com/en-us/library/ff637436.aspx \|title=New Features in Visual Basic 10 \|date=June 3, 2010 \|access-date=September 5, 2015 \|archive-date=March 4, 2016 \|archive-url=https://web.archive.org/web/20160304231731/https://msdn.microsoft.com/en-us/library/ff637436.aspx \|url-status=live }}</ref>
	* The [[equals sign]] ("=") is used in both assigning values to variables and in comparison.		* The [[equals sign]] ("=") is used in both assigning values to variables and in comparison.
Line 82:		Line 82:
	This line performs the actual task of writing the output. ''Console'' is a system object, representing a command-line interface (also known as a "console") and granting programmatic access to the operating system's [[standard streams]]. The program calls the ''Console'' method ''WriteLine,'' which causes the string passed to it to be displayed on the console.		This line performs the actual task of writing the output. ''Console'' is a system object, representing a command-line interface (also known as a "console") and granting programmatic access to the operating system's [[standard streams]]. The program calls the ''Console'' method ''WriteLine,'' which causes the string passed to it to be displayed on the console.

	Instead of Console.WriteLine, ~~one could use~~ MsgBox, which prints the message in a dialog box instead of a command-line window.<ref>{{cite web \|url=http://msdn.microsoft.com/en-us/library/3cf7t4xt(VS.80).aspx \|title=Visual Basic Version of Hello, World \|publisher=MSDN – Developer Center \|access-date=January 20, 2010 \|archive-date=January 11, 2010 \|archive-url=https://web.archive.org/web/20100111152427/http://msdn.microsoft.com/en-us/library/3cf7t4xt(VS.80).aspx \|url-status=live }}</ref>		Instead of Console.WriteLine, an alternative is MsgBox, which prints the message in a dialog box instead of a command-line window.<ref>{{cite web \|url=http://msdn.microsoft.com/en-us/library/3cf7t4xt(VS.80).aspx \|title=Visual Basic Version of Hello, World \|publisher=MSDN – Developer Center \|access-date=January 20, 2010 \|archive-date=January 11, 2010 \|archive-url=https://web.archive.org/web/20100111152427/http://msdn.microsoft.com/en-us/library/3cf7t4xt(VS.80).aspx \|url-status=live }}</ref>

	=== Complex example ===		=== Complex example ===
Line 129:		Line 129:
	=== Comparison with the classic Visual Basic ===		=== Comparison with the classic Visual Basic ===
	{{Main\|Comparison of Visual Basic and Visual Basic .NET}}		{{Main\|Comparison of Visual Basic and Visual Basic .NET}}
	Whether Visual Basic .NET should be considered as just another version of Visual Basic or a completely different language is a topic of debate. There are new additions to support new features, such as [[exception handling\|structured exception handling]] and short-circuited expressions. Also, two important data-type changes occurred with the move to VB.NET: compared to Visual Basic 6, the <code>Integer</code> [[data type]] has been doubled in length from 16 bits to 32 bits, and the <code>Long</code> [[data type]] has been doubled in length from 32 bits to 64 bits. This is true for all versions of VB.NET. A 16-bit integer in all versions of VB.NET is now known as a <code>Short</code>. Similarly, the [[Windows Forms]] editor is very similar in style and function to the Visual Basic form editor.		Whether Visual Basic .NET should be considered as just another version of Visual Basic or a completely different language is a topic of debate. There are new additions to support new features, such as [[exception handling\|structured exception handling]] and short-circuited expressions. Also, two important data-type changes occurred with the move to VB.NET: compared to Visual Basic 6, the <code>[[Integer (computer science)\|Integer]]</code> [[data type]] has been doubled in length from 16 bits to 32 bits, and the <code>Long</code> [[data type]] has been doubled in length from 32 bits to 64 bits. This is true for all versions of VB.NET. A 16-bit integer in all versions of VB.NET is now known as a <code>Short</code>. Similarly, the [[Windows Forms]] editor is very similar in style and function to the Visual Basic form editor.

	The things that ''have'' changed significantly are the semantics—from those of an object-based programming language running on a [[deterministic]], [[reference counting\|reference-counted]] engine based on [[Component Object Model\|COM]] to a fully [[object-oriented]] language backed by the [[.NET Framework]], which consists of a combination of the [[Common Language Runtime]] (a [[virtual machine]] using [[Garbage collection (computer science)#Generational GC (aka Ephemeral GC)\|generational garbage collection]] and a [[just-in-time compilation]] engine) and a far larger [[class library]]. The increased breadth of the latter was also a problem that VB developers had to deal with when coming to the language, although this was somewhat addressed by the ''My'' feature in Visual Studio 2005.		The things that ''have'' changed significantly are the semantics—from those of an object-based programming language running on a [[deterministic]], [[reference counting\|reference-counted]] engine based on [[Component Object Model\|COM]] to a fully [[Object-oriented programming\|object-oriented]] language backed by the [[.NET Framework]], which consists of a combination of the [[Common Language Runtime]] (a [[virtual machine]] using [[Garbage collection (computer science)#Generational GC (aka Ephemeral GC)\|generational garbage collection]] and a [[just-in-time compilation]] engine) and a far larger [[class library]]. The increased breadth of the latter was also a problem that VB developers had to deal with when coming to the language, although this was somewhat addressed by the ''My'' feature in Visual Studio 2005.

	The changes altered many underlying assumptions about the "right" thing to do with respect to the performance and maintainability of applications. Some functions and libraries no longer exist; others are available, but not as efficient as the "native" .NET alternatives. Even if they compiled, most converted Visual Basic 6 applications required some level of [[refactoring]] to take full advantage of the .NET language. Microsoft provided documentation to cover changes in language syntax, debugging applications, deployment, and terminology.<ref>{{cite web\|url = http://msdn.microsoft.com/en-us/vstudio/ms788233\|title = Microsoft Visual Basic 6.0 Migration Resource Center\|access-date = November 9, 2014\|website = [[MSDN]]\|publisher = [[Microsoft]]\|archive-date = November 9, 2014\|archive-url = https://web.archive.org/web/20141109140433/http://msdn.microsoft.com/en-us/vstudio/ms788233\|url-status = live}}</ref> A popular trade book designed to ease the transition was [[Michael Halvorson\|Michael Halvorson's]] ''Microsoft Visual Basic .NET Professional Step by Step'', published in 2002 by [[Microsoft Press]].		The changes altered many underlying assumptions about the "right" thing to do with respect to the performance and maintainability of applications. Some functions and libraries no longer exist; others are available, but not as efficient as the "native" .NET alternatives. Even if they compiled, most converted Visual Basic 6 applications required some level of [[refactoring]] to take full advantage of the .NET language. Microsoft provided documentation to cover changes in language syntax, debugging applications, deployment, and terminology.<ref>{{cite web\|url = http://msdn.microsoft.com/en-us/vstudio/ms788233\|title = Microsoft Visual Basic 6.0 Migration Resource Center\|access-date = November 9, 2014\|website = [[MSDN]]\|publisher = [[Microsoft]]\|archive-date = November 9, 2014\|archive-url = https://web.archive.org/web/20141109140433/http://msdn.microsoft.com/en-us/vstudio/ms788233\|url-status = live}}</ref> A popular trade book designed to ease the transition was [[Michael Halvorson\|Michael Halvorson's]] ''Microsoft Visual Basic .NET Professional Step by Step'', published in 2002 by [[Microsoft Press]].
Line 202:		Line 202:
	{{Main\|Comparison of C Sharp and Visual Basic .NET}}		{{Main\|Comparison of C Sharp and Visual Basic .NET}}

	C# and Visual Basic are Microsoft's first languages made to program on the .NET Framework (later adding [[F Sharp (programming language)\|F#]] and more; others have also added languages). Though C# and Visual Basic are syntactically different, that is where the differences mostly end. Microsoft developed both of these languages to be part of the same .NET Framework development platform. They are both developed, managed, and supported by the same language development team at Microsoft.<ref>{{cite web \|last=Krill \|first=Paul \|url=http://www.infoworld.com/article/09/02/27/Microsoft_converging_programming_languages_1.html?R=printThis&A=/article/09/02/27/Microsoft_converging_programming_languages_1.html \|archive-url=https://archive.today/20130126074556/http://www.infoworld.com/article/09/02/27/Microsoft_converging_programming_languages_1.html?R=printThis&A=/article/09/02/27/Microsoft_converging_programming_languages_1.html \|url-status=dead \|archive-date=January 26, 2013 \|title=Microsoft converging programming languages \| Developer World \|publisher=InfoWorld \|date=February 27, 2009 \|access-date=August 18, 2013 }}</ref> They compile to the same intermediate language (IL), which runs against the same .NET Framework runtime libraries.<ref>{{cite web \|url=http://www.dotnet-guide.com/msintermediate.html \|title=Microsoft Intermediate Language \|publisher=Dotnet-guide.com \|access-date=August 18, 2013 \|archive-date=June 2, 2013 \|archive-url=https://web.archive.org/web/20130602151947/http://www.dotnet-guide.com/msintermediate.html \|url-status=live }}</ref> Although there are some differences in the programming constructs, their differences are primarily syntactic and, assuming one avoids the Visual Basic "Compatibility" libraries provided by Microsoft to aid conversion from Visual Basic 6, almost every feature in VB has an equivalent feature in C# and vice versa. ~~Lastly, both~~ languages reference the same Base Classes of the .NET Framework to extend their functionality. As a result, with few exceptions, a program written in either language can be run through a simple syntax converter to translate to the other. There are many open source and commercially available products for this task.		C# and Visual Basic are Microsoft's first languages made to program on the .NET Framework (later adding [[F Sharp (programming language)\|F#]] and more; others have also added languages). Though C# and Visual Basic are syntactically different, that is where the differences mostly end. Microsoft developed both of these languages to be part of the same .NET Framework development platform. They are both developed, managed, and supported by the same language development team at Microsoft.<ref>{{cite web \|last=Krill \|first=Paul \|url=http://www.infoworld.com/article/09/02/27/Microsoft_converging_programming_languages_1.html?R=printThis&A=/article/09/02/27/Microsoft_converging_programming_languages_1.html \|archive-url=https://archive.today/20130126074556/http://www.infoworld.com/article/09/02/27/Microsoft_converging_programming_languages_1.html?R=printThis&A=/article/09/02/27/Microsoft_converging_programming_languages_1.html \|url-status=dead \|archive-date=January 26, 2013 \|title=Microsoft converging programming languages \| Developer World \|publisher=InfoWorld \|date=February 27, 2009 \|access-date=August 18, 2013 }}</ref> They compile to the same intermediate language (IL) known as [[Common Intermediate Language\|CIL]], which runs against the same .NET Framework runtime libraries.<ref>{{cite web \|url=http://www.dotnet-guide.com/msintermediate.html \|title=Microsoft Intermediate Language \|publisher=Dotnet-guide.com \|access-date=August 18, 2013 \|archive-date=June 2, 2013 \|archive-url=https://web.archive.org/web/20130602151947/http://www.dotnet-guide.com/msintermediate.html \|url-status=live }}</ref> Although there are some differences in the programming constructs, their differences are primarily syntactic and, assuming one avoids the Visual Basic "Compatibility" libraries provided by Microsoft to aid conversion from Visual Basic 6, almost every feature in VB has an equivalent feature in C# and vice versa. Both languages reference the same Base Classes of the .NET Framework to extend their functionality, and both languages can reference compiled code written in the other language. As a result, with few exceptions, a program written in either language can be run through a simple syntax converter to translate to the other. There are many open source and commercially available products for this task.

	== Examples ==		== Examples ==
Line 241:		Line 241:
	CreateObject("Sapi.Spvoice").Speak(TextBox1.Text)		CreateObject("Sapi.Spvoice").Speak(TextBox1.Text)
	End Sub		End Sub
	End Class		End Class
	</syntaxhighlight>		</syntaxhighlight>

Line 266:		Line 266:

	=== 2003 (VB 7.1) ===		=== 2003 (VB 7.1) ===
	Visual Basic .NET 2003 was released with [[.NET Framework 1.1]]. New features included support for the [[.NET Compact Framework]] and a better VB upgrade [[wizard (software)\|wizard]]. Improvements were also made to the performance and reliability of .NET IDE (particularly the [http://msdn.microsoft.com/msdnmag/issues/05/06/AdvancedBasics/default.aspx background compiler]) and runtime. In addition, Visual Basic .NET 2003 was available in the Visual Studio.NET Academic Edition, distributed to a certain number of scholars~~{{weasel inline\|date=February 2014}}~~ from each country without cost.		Visual Basic .NET 2003 was released with [[.NET Framework 1.1]]. New features included support for the [[.NET Compact Framework]] and a better VB upgrade [[wizard (software)\|wizard]]. Improvements were also made to the performance and reliability of .NET IDE (particularly the [http://msdn.microsoft.com/msdnmag/issues/05/06/AdvancedBasics/default.aspx background compiler]) and runtime. In addition, Visual Basic .NET 2003 was available in the Visual Studio.NET Academic Edition, distributed to a certain number of scholars from each country without cost.

	=== 2005 (VB 8.0) ===		=== 2005 (VB 8.0) ===

Visual Basic (.NET) - Revision history

imported>Deshadow123: Undid revision 1326708498 by ~2025-39798-69 (talk) undid

imported>IndependentCharm83: Added links to other articles, minor grammar fixes and editing, and added a fact about being able to reference VB code from C# and vice versa

imported>Adfontes18: /* Comparison with the classic Visual Basic */ Changes to tense reflect the fact that this transition to .NET happened over 20 years ago.

← Previous revision	Revision as of 11:46, 10 December 2025
(No difference)