SlashPos = InStr(LastPos + 1, SourceFile, "\")Įnd If Loop ' Now return last 'LastPos' chars from the original SourceFile string ' Dim SlashPos As Integer Dim LastPos As Integer ' Find out the position index for the last slash character (LastPos) "GetModuleHandleA" ( ByVal lpModuleName As String) As Long Private Function GetFileFromFullName( ByVal SourceFile As String) As String ' ' Return the file name and extension part of SourceFile. Private Declare Function GetModuleFileName Lib "kernel32" _Īlias "GetModuleFileNameA" ( ByVal hModule As Long, _īyVal lpFileName As String, ByVal nSize As Long) As Long Private Declare Function GetModuleHandle Lib "kernel32" Alias _ I have used this code to test if my application was running in IDE with VB6, but I know there were other (maybe simpler) ways to do it.įirst, some helper routines and declarations.
Just for the comparison I went through my "Old Code Archive" and under the dust I found how the same test was done with VB6. ''' ''' Returns boolean value telling if the application is running under IDE ''' ''' True if the application is running under IDE ''' Public Function RunningUnderIDE() As Boolean ' Return ()Įnd Function Test with Visual Basic 6 if running under IDE This is the case when your application runs in IDE. From Debugger class you can check IsAttached property which tells if a debugger is attached to the running process. System.Diagnostics namespace contains Debugger class. With VB.NET it's quite simple to test if the application runs in IDE. But when you hand your application over to testers, they like to have your application behaving like end users would see it. When you debug application under IDE, it can use extensive debug information dumping. When running as a standalone application it can use path to real data.Īnother scenario where your application can use this information, is to display debugging information. Under IDE the application can use path to some data made for debugging purpose. One scenario would be to use different paths to data files. When the application can check if it's running under IDE or as a standalone application, it can make different decisions based on that knowledge. Your application does not know it but in some cases it should know that it's running under IDE. When you write your VB.NET application and debug it under IDE, you know it's running under IDE.
0 kommentar(er)
