App Object Changes in Visual Basic .NET
TOC
Collapse the table of content
Expand the table of content

App Object Changes in Visual Basic .NET

Visual Studio .NET 2003

The App object in Visual Basic 6.0 was a global object used to set or retrieve information about the application. There is no direct equivalent for the App object in Visual Basic .NET; however, most of the properties can be mapped to equivalent properties in the .NET Framework.

Note   The App object's Version Information properties are replaced by Assembly attributes in Visual Basic .NET. Version Information properties were set in the Project Properties dialog box; Assembly attributes are set by editing the AssemblyInfo file in the Visual Basic .NET project. For more information, see Attributes.

App Object Properties

Visual Basic 6.0Visual Basic .NET Equivalent
CommentsAssemblyDescription attribute
CompanyNameAssemblyCompany attribute
EXENameSystem.Reflection.Assembly.GetExecutingAssembly.Location
Note   The Location property returns the full path including the file name; the EXEName property returned only the file name.
FileDescriptionSystem.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).FileDescription
HelpFileNo equivalent. For more information, see Help Support Changes in Visual Basic .NET.
HInstanceSystem.Runtime.InteropServices.Marshal.GetHINSTANCE(System.Reflection.Assembly.GetExecutingAssembly.GetModules()(0)).ToInt32
LegalCopyrightSystem.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).LegalCopyright
LegalTrademarksSystem.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).LegalTrademarks
LogEvent methodNo equivalent. Logging in Visual Basic .NET is handled via Event Logs. For more information, see Creating and Removing Custom Event Logs.
LogModeNo equivalent. Logging in Visual Basic .NET is handled via Event Logs. For more information, see Creating and Removing Custom Event Logs.
LogPathNo equivalent. Logging in Visual Basic .NET is handled via Event Logs. For more information, see Creating and Removing Custom Event Logs.
MajorSystem.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).FileMajorPart
Note   The format for version numbers is different in Visual Basic .NET. For more information, see Version Numbering Changes in Visual Basic .NET.
MinorSystem.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).FileMinorPart
Note   The format for version numbers is different in Visual Basic .NET. For more information, see Version Numbering Changes in Visual Basic .NET.
NonModalAllowedNo equivalent. This was a read-only property related to ActiveX .dll files. The .NET common language runtime automatically manages this behavior.
OleRequestPendingMsgTextNo equivalent. This property relates to OLE automation, which is not supported by Visual Basic .NET.
OleRequestPendingMsgTitleNo equivalent. This property relates to OLE automation, which is not supported by Visual Basic .NET.
OleRequestPendingTimeoutNo equivalent. This property relates to OLE automation, which is not supported by Visual Basic .NET.
OleServerBusyMsgTextNo equivalent. This property relates to OLE automation, which is not supported by Visual Basic .NET.
OleServerBusyMsgTitleNo equivalent. This property relates to OLE automation, which is not supported by Visual Basic .NET.
OleServerBusyRaiseErrorNo equivalent. This property relates to OLE automation, which is not supported by Visual Basic .NET.
OleServerBusyTimeoutNo equivalent. This property relates to OLE automation, which is not supported by Visual Basic .NET.
PathSystem.Reflection.Assembly.GetExecutingAssembly.Location
Note   The Location property returns the full path including the file name; the Path property returned only the path.
PrevInstanceNo equivalent. For more information, see PrevInstance Property Changes in Visual Basic .NET.
ProductNameSystem.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).ProductName
RetainedProjectNo equivalent. Visual Basic .NET does not have the ability to retain a project in memory.
RevisionSystem.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).FileBuildPart

– or –

System.Diagnostics.FileVersionInfo.GetVersionInfo(System.Reflection.Assembly.GetExecutingAssembly.Location).FilePrivatePart

Note   The format for version numbers is different in Visual Basic .NET. For more information, see Version Numbering Changes in Visual Basic .NET.
StartLogging methodNo equivalent. Logging in Visual Basic .NET is handled via Event Logs. For more information, see Creating and Removing Custom Event Logs.
StartModeNo equivalent. In Visual Basic 6.0, this property was used to start an application as an ActiveX component. ActiveX component creation is not supported in Visual Studio .NET.
TaskVisibleNo equivalent. For more information, see TaskVisible Property Changes in Visual Basic .NET.
ThreadIDNo equivalent. The threading model is different in Visual Basic .NET.
TitleNo equivalent. In Visual Basic .NET, the Text property of the main form in the application determines the title that will be shown in the Task Manager.
UnattendedAppNo equivalent. For unattended applications in Visual Basic .NET, choose a Console Application project.

See Also

Control Changes in Visual Basic .NET | Screen Object Changes in Visual Basic .NET

Show:
© 2016 Microsoft