Changing Font Properties in VB.NET

Changing Font Properties in VB.NET Strong is perused distinctly in VB.NET. This article reveals to you how to change that. In VB6, it was dead simple to change a text style to strong. You essentially coded something like Label1.FontBold, yet in VB.NET, the Bold property of the Font object for a Label is perused as it were. So how would you change it? Changing Font Properties in VB.NET With Windows Forms Heres the fundamental code design for Windows Forms. Private Sub BoldCheckbox_CheckedChanged( _ByVal sender As System.Object, _ByVal e As System.EventArgs) _Handles BoldCheckbox.CheckedChangedIf BoldCheckbox.CheckState CheckState.Checked ThenTextToBeBold.Font _New Font(TextToBeBold.Font, FontStyle.Bold)ElseTextToBeBold.Font _New Font(TextToBeBold.Font, FontStyle.Regular)End IfEnd Sub Theres much more than Label1.FontBold, that is without a doubt. In .NET, textual styles are unchanging. That implies once they are made they can't be refreshed. VB.NET gives you more control than you get with VB6 over what your program is doing, however the expense is that you need to compose the code to gain that power. VB6 will inside drop one GDI text style asset and make another one. With VB.NET, you need to do it without anyone's help. You can make things somewhat more worldwide by including a worldwide statement at the highest point of your structure: Private fBold As New Font(Arial, FontStyle.Bold)Private fNormal As New Font(Arial, FontStyle.Regular) At that point you can code: TextToBeBold.Font fBold Note that the worldwide statement presently indicates the textual style family, Arial, as opposed to just utilizing the current text style group of one explicit control. Utilizing WPF Shouldn't something be said about WPF? WPF is a graphical subsystem you can use with the .NET Framework to construct applications where the UI depends on a XML language called XAML and the code is isolated from the plan and depends on a .NET language like Visual Basic. In WPF, Microsoft changed the procedure once more. Heres the manner in which you do something very similar in WPF. Private Sub BoldCheckbox_Checked( _ByVal sender As System.Object, _ByVal e As System.Windows.RoutedEventArgs) _Handles BoldCheckbox.CheckedIf BoldCheckbox.IsChecked True ThenTextToBeBold.FontWeight FontWeights.BoldElseTextToBeBold.FontWeight FontWeights.NormalEnd IfEnd Sub The progressions are: The CheckBox occasion is Checked rather than CheckedChangedThe CheckBox property is IsChecked rather than CheckStateThe property estimation is a Boolean True/False rather than the Enum CheckState. (Windows Forms offers a True/False Checked property notwithstanding CheckState, however WPF doesnt have both.)FontWeight is a reliance property of the Label rather than FontStyle being the property of the Font object.FontWeights is a NotInheritable class and Bold is a Static incentive in that class Whew!! Do you think Microsoftâ actually attempted to make it all the more befuddling?