DotNetNewsgroup.com  
web access to complete list of Microsoft.NET newsgroups
   home   |   control panel login   |   archive  |  
 
  carried group
academic
adonet
aspnet
aspnet.announcements
aspnet.buildingcontrols
aspnet.caching
aspnet.datagridcontrol
aspnet.mobile
aspnet.security
aspnet.webcontrols
aspnet.webservices
assignment_manager
datatools
dotnet.distributed_apps
dotnet.general
dotnet.myservices
dotnet.nternationalization
dotnet.scripting
dotnet.security
dotnet.vjsharp
dotnet.vsa
dotnet.xml
dotnetfaqs
framework
framework.clr
framework.compactframework
framework.component_services
framework.controls
framework.databinding
framework.drawing
framework.enhancements
framework.interop
framework.odbcnet
framework.performance
framework.remoting
framework.sdk
framework.setup
framework.webservices
framework.windowsforms
framework.wmi
frwk.windowsforms.designtime
lang.csharp
lang.jscript
lang.vb
lang.vb.controls
lang.vb.data
lang.vb.upgrade
lang.vc
lang.vc.libraries
  
 
start date: Thu, 2 Aug 2007 16:44:01 -0400,    posted on: microsoft.public.dotnet.framework        back       

Thread Index
  1    WNC


C# .Net ActiveX COM Interop problem   
I have a C# .NET program that uses COM Interop to use an ActiveX control 
(the control is hosted on the main form).  I have successfully used the 
debug version of this program on four different computers in my office 
(Win2K Server, Windows XP SP1 and Windows XP SP2).  I just got a new 
computer running Windows XP SP2.  The same ActiveX control is installed on 
all the computers, and I know it's registered.  On the new computer, I get 
the following error when I try to run the program:

3 System.Object ForwardCallToInvokeMember(System.String, 
System.Reflection.BindingFlags, System.Object, Int32[], 
System.Runtime.Remoting.Proxies.MessageData ByRef)   at 
System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags 
flags, Object target, Int32[] aWrapperTypes, MessageData& msgData) at 
TWSLib._DTws.connect(String host, Int32 port, Int32 clientId) at 
AxTWSLib.AxTws.connect(String host, Int32 port, Int32 clientId) at 
IB_API_IInterface.MainClass.Connect(Form1 frm) in E:\(path to the 
program)\Form1.cs:line 535

I've googled this issue and found some entries, but nothing explains why 
this error occurs only on this new computer.  Would it help to compile a 
release version and deploy that instead of the debug version?  But it still 
doesn't answer why this happens on only one computer, which is configured 
exactly like the other WinXP machines.

Any ideas would be most appreciated.
Date:Thu, 2 Aug 2007 16:44:01 -0400   Author:  

Google
 
Web dotnetnewsgroup.com


COPYRIGHT ?2005, EUROFRONT WORLDWIDE LTD., ALL RIGHT RESERVE  |   Contact us