| Security Unless an addin is signed with a strong name key and loaded into the global assembly cache it will run with very restricted access. E.g the permission set "Internet". Error codes: 8013150A = An error relating to security occurred. (COR_E_SECURITY) More info about how strong naming works can be found here. Sending Messages (Limitations) You can only send messages in the IncomingTextMessage event. And only to the person who sent you the message. This means you can't have for example a timer sending out a message to someone every X hours. Or forwarding all messages from Bill to Bull Error codes: 810003DF = Attempt sending message to different user 810003E1 = Attempt sending multiple messages 810003E0 = Attempt sending message outside event Debugging If you set the registry key PromptForDebugger (dword) in HKCU\Software\Microsoft\MSNMessener\AddInDebugHooks\ to 1 messenger will display an empty message box before it loads so you can attach the debugger to the process before you continue. Or you can configure visual studio to run your add in class library with an external program, select the messenger exe and then press F5 (run with debugger). I've found it easier to develop non specific messenger code in a test application and when I know that works add it to the add-in. Especially since messenger has a bad habit of not releasing the file lock on the dll even after you unload it so you have to restart it every time you want to compile. Links MSDN Documentation Katie Blanch's Blog |