Support.FontChangeName(Font, String) Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Caution
Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862
Returns a new Font for a given Visual Basic 6.0 Font.
public:
static System::Drawing::Font ^ FontChangeName(System::Drawing::Font ^ CurrentFont, System::String ^ Name);public static System.Drawing.Font FontChangeName (System.Drawing.Font CurrentFont, string Name);[System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")]
public static System.Drawing.Font FontChangeName (System.Drawing.Font CurrentFont, string Name);static member FontChangeName : System.Drawing.Font * string -> System.Drawing.Font[<System.Obsolete("Microsoft.VisualBasic.Compatibility.* classes are obsolete and supported within 32 bit processes only. http://go.microsoft.com/fwlink/?linkid=160862")>]
static member FontChangeName : System.Drawing.Font * string -> System.Drawing.FontPublic Function FontChangeName (CurrentFont As Font, Name As String) As FontParameters
- Name
- String
A String that represents the Visual Basic 6.0 Font property.
Returns
A Font that matches the Visual Basic 6.0 Font.
- Attributes
Remarks
In Visual Basic 6.0, the name of a font was specified by the Font property; in Visual Basic, Name is a property of the Font object. This function is used by the upgrade tools to convert a Visual Basic 6.0 Font to a Font.
Note
Functions and objects in the Microsoft.VisualBasic.Compatibility.VB6 namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic 2008. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.
