Connecttonewobject and connection to assembly
Just trying to clarify something...
I have created a VB.net assembly which connects to MS exchange for email/calendar purposes.
Using PB 12.5 I create an instance of an object, issue a connecttonewobject which is the DLL (assembly),
then connecting to exchange using user email id and password and retrieve and send emails with no issues.
Here's is where it gets messy..
IF I create a second instance of the object, issue a connecttonewobject to the same DLL but this time connect to exchange using a different user id and password then ... when I try to get emails from either instance of the object it is only looking at the connection of the user id that was last connected.
Basically I need to connect to exchange using the assembly with 2 different email accounts. So I assumed if I create two instances of the object and connect that I would have two distinct connections. Looks like when the second connection occurs it detects that the assembly is running and reuses it to connect to the second email account... in turn I lose the first email account connection.
Am I understanding this correctly or should I in-fact have two separate connections.
Do I need to have two distinctly named assemblies for this to work.. One for first user email account and a 2nd one for the other email account?
(hope its not too confusing)