brian
06-23-2003, 04:24 PM
Hi,
An error message pops up every time I build a .net project:
-----
NullReferenceException
Exception:
Object reference not set to an instance of an object.
Stack trace:
at EnvDTE.Commands.AddnamedCommand(AddIn AddInInstance, String Name, String ButtonText, String Tooltip, Boolean MsOButton, Int32 Bitmap, Object[]& ContextUIGUIDs, Int32 vsCommandDisabledFlagsValue)
at InterfaceImplementer.Connect.OnConnection(Object application, ext_ConnectMode connectMode, Object addInInst, Array& custom)
-----
Then after I close this error box, the step goes on and builds successfully. I have dozens of modules to build, so sit there and close each message box is a big waste of time.
I get the same error on both Visual Build 4.0a, Visual Build 5.0 when building C#, C++, VB.net, Windows Application projects, and Class Library projects.
My environment is Windows 2000 SP3 with .NET FrameWork version 1.0 SP2.
The problem is reproducible in 2 different computers having the same setup as described above. However, when I tried with windows XP, the message box did not appear. I wonder if this is a windows 200 only problem.
Thanks
Brian
An error message pops up every time I build a .net project:
-----
NullReferenceException
Exception:
Object reference not set to an instance of an object.
Stack trace:
at EnvDTE.Commands.AddnamedCommand(AddIn AddInInstance, String Name, String ButtonText, String Tooltip, Boolean MsOButton, Int32 Bitmap, Object[]& ContextUIGUIDs, Int32 vsCommandDisabledFlagsValue)
at InterfaceImplementer.Connect.OnConnection(Object application, ext_ConnectMode connectMode, Object addInInst, Array& custom)
-----
Then after I close this error box, the step goes on and builds successfully. I have dozens of modules to build, so sit there and close each message box is a big waste of time.
I get the same error on both Visual Build 4.0a, Visual Build 5.0 when building C#, C++, VB.net, Windows Application projects, and Class Library projects.
My environment is Windows 2000 SP3 with .NET FrameWork version 1.0 SP2.
The problem is reproducible in 2 different computers having the same setup as described above. However, when I tried with windows XP, the message box did not appear. I wonder if this is a windows 200 only problem.
Thanks
Brian