Hi everyone,
I´m trying to create client activated objects (CAO) from a client that doesn´t have the code of the classes served by the server. For that purpose, I use the SOAPSUDS.exe tool, in order to generate the proxy for the dll which has the actual source code. To this point, I have no problem if I use the Visual Studio .NET 2002, but it doesn´t run in VS 2003!
I obtain an error like this when I try to instantiate the remote object: "Permission denied for activating type soap: clsClass1". The client has a reference to the proxy dll generated by SOAPSUDS (SOAPSUDS -ia:Common -oa:CommonProxy.dll), and the server and client code is this:
Server:
RemotingConfiguration.RegisterActivatedServiceType(GetType(clsClass1))
Client:
RemotingConfiguration.RegisterActivatedClientType(GetType(clsClass1), "
obj1 = New clsClass1
Any information about this different behaviour between the 2002 and 2003 versions of VS .NET??
Thanks.
I´m trying to create client activated objects (CAO) from a client that doesn´t have the code of the classes served by the server. For that purpose, I use the SOAPSUDS.exe tool, in order to generate the proxy for the dll which has the actual source code. To this point, I have no problem if I use the Visual Studio .NET 2002, but it doesn´t run in VS 2003!
I obtain an error like this when I try to instantiate the remote object: "Permission denied for activating type soap: clsClass1". The client has a reference to the proxy dll generated by SOAPSUDS (SOAPSUDS -ia:Common -oa:CommonProxy.dll), and the server and client code is this:
Server:
RemotingConfiguration.RegisterActivatedServiceType(GetType(clsClass1))
Client:
RemotingConfiguration.RegisterActivatedClientType(GetType(clsClass1), "
obj1 = New clsClass1
Any information about this different behaviour between the 2002 and 2003 versions of VS .NET??
Thanks.