How to Resolve 'Computer' is ambiguous between declarations in Modules 'GlbSoft.SWB.SS.My.MyProject' and 'GlbSoft.SWB.SS.My.MyProject'
-
I am trying to access the current NUM LOCK setting on a computer running VBA/VB.NET: - Windows 7 - Visual Studio 2010 - Microsoft (Office) Excel 2010 Here is the code:
**Public Const _GlobalDefinitions As String = "GlobalDefinitions"
Public Declare Sub keybd_event Lib "user32" (ByVal bVk As Byte, ByVal bScan As Byte, ByVal dwFlags As Integer, ByVal dwExtraInfo As Integer)
Public Const VK_NUMLOCK As Integer = &H90
Public Const KEYEVENTF_EXTENDEDKEY As Integer = &H1
Public Const KEYEVENTF_KEYUP As Integer = &H2
Public InitialNumLockState As BooleanPublic Sub CheckNumLockState(Optional mWriteback As SSWriteback = Nothing)
Try
If InitialNumLockState Then
If Not My.Computer.Keyboard.NumLock Then
keybd_event(VK_NUMLOCK, &H45, KEYEVENTF_EXTENDEDKEY Or 0, 0)
keybd_event(VK_NUMLOCK, &H45, KEYEVENTF_EXTENDEDKEY Or KEYEVENTF_KEYUP, 0)
End If
End If
Catch ex As Exception
If Not mWriteback Is Nothing Then
AddToErrorLog(mWriteback, _GlobalDefinitions & ":" & System.Reflection.MethodBase.GetCurrentMethod.Name.ToString & "> " & ex.Message & ", " & ex.StackTrace, TraceEventType.Error)
End If
End Try
End Sub**The InitialNumLockState variable is set earlier in the process as follows: InitialNumLockState = My.Computer.Keyboard.NumLock The initial reference to My.Computer.KeyBoard.NumLock works fine (and I can query it within a Watch window in runtime) and initializes the InitialNumLockState variable, e.g., True if the NUM LOCK key is ON. In the second reference to My.Computer.KeyBoard.NumLock, however, I am getting the following error: 'Computer' is ambiguous between declarations in Modules 'GlbSoft.SWB.SS.My.MyProject' and 'GlbSoft.SWB.SS.My.MyProject'. Note that the error message says the reference is ambiguous because it is present in two modules with the same name. Of course, this is not possible. There is only one project/namespace involved (GSI_SWB_SS/GlbSoft.SWB.SS). I have tried a number of different approaches, all without success. Does anyone have any ideas or insight concerning this error and what can possibly be looked at in order to resolve it? Thanks in advance, Chris Fleetwood
-
I am trying to access the current NUM LOCK setting on a computer running VBA/VB.NET: - Windows 7 - Visual Studio 2010 - Microsoft (Office) Excel 2010 Here is the code:
**Public Const _GlobalDefinitions As String = "GlobalDefinitions"
Public Declare Sub keybd_event Lib "user32" (ByVal bVk As Byte, ByVal bScan As Byte, ByVal dwFlags As Integer, ByVal dwExtraInfo As Integer)
Public Const VK_NUMLOCK As Integer = &H90
Public Const KEYEVENTF_EXTENDEDKEY As Integer = &H1
Public Const KEYEVENTF_KEYUP As Integer = &H2
Public InitialNumLockState As BooleanPublic Sub CheckNumLockState(Optional mWriteback As SSWriteback = Nothing)
Try
If InitialNumLockState Then
If Not My.Computer.Keyboard.NumLock Then
keybd_event(VK_NUMLOCK, &H45, KEYEVENTF_EXTENDEDKEY Or 0, 0)
keybd_event(VK_NUMLOCK, &H45, KEYEVENTF_EXTENDEDKEY Or KEYEVENTF_KEYUP, 0)
End If
End If
Catch ex As Exception
If Not mWriteback Is Nothing Then
AddToErrorLog(mWriteback, _GlobalDefinitions & ":" & System.Reflection.MethodBase.GetCurrentMethod.Name.ToString & "> " & ex.Message & ", " & ex.StackTrace, TraceEventType.Error)
End If
End Try
End Sub**The InitialNumLockState variable is set earlier in the process as follows: InitialNumLockState = My.Computer.Keyboard.NumLock The initial reference to My.Computer.KeyBoard.NumLock works fine (and I can query it within a Watch window in runtime) and initializes the InitialNumLockState variable, e.g., True if the NUM LOCK key is ON. In the second reference to My.Computer.KeyBoard.NumLock, however, I am getting the following error: 'Computer' is ambiguous between declarations in Modules 'GlbSoft.SWB.SS.My.MyProject' and 'GlbSoft.SWB.SS.My.MyProject'. Note that the error message says the reference is ambiguous because it is present in two modules with the same name. Of course, this is not possible. There is only one project/namespace involved (GSI_SWB_SS/GlbSoft.SWB.SS). I have tried a number of different approaches, all without success. Does anyone have any ideas or insight concerning this error and what can possibly be looked at in order to resolve it? Thanks in advance, Chris Fleetwood
Looks more like a Visual Studio problem. Clean the solution, close VS, delete old local files, and re-build the solution again. That should normally help.