[2005] COM Error (redemption.dll)
Hello,
I wonder if anyone can help me please ?
I have some code which is used to send e-mails automatically to my employees.
As the e-mails will be send to many employees as once, I don't want the Microsoft security message to pop up each time.
Code:
Private _outlookApplication As Outlook.Application
Dim _outlookProfile As String = "Default Outlook Profile"
_outlookApplication = New Outlook.Application()
Dim _message As Outlook.MailItem
Dim _secureMessage As New Redemption.SafeMailItem
_message = _outlookApplication.CreateItem(Outlook.OlItemType.olMailItem)
_secureMessage.Item = _message
_secureMessage.Recipients.Add(m_EmailAddress)
_secureMessage.Subject = m_Subject
_secureMessage.Body = m_Body
_secureMessage.Send()
_secureMessage = Nothing
_message = Nothing
_outlookApplication = Nothing
In order to get round the problem, I am referencing 'Redemption.dll' which is working fine on my machine (at least it is now that I have registered the dll using REGSRV32)
However if I try the same code on another machine (one where this hasn't been registered) I get the following error :
"Retrieving the com class factory for component with clsid {........} failed due to the following error : 80040154""
Obviously if I register this file on the other machine, I'm sure it would get round the probem - however I don't know how to do this automatically.
I'm using ClickOnce if this helps.
Re: [2005] COM Error (redemption.dll)
ClickOnce does not allow for using COM components because ClickOnce does not support writing to the registry or doing anything that requires administrative rights on the system.
Here is a list of things you should consider about your app, and if any of them are true, then clickonce is not for you.
Quote:
Does your application require user input at installation?
Does your application require configuration of Active Directory or COM+?
After your application is installed, does it create files, write to the registry, or affect the target system in a way that leaves resources behind when your application is removed?
Does your application install COM components?
Does your application require registering any components for COM Interop?
Does your application install any services?
Must your application install to a specific location or install assemblies to the Global Assembly Cache?
Does your application have any components that are conditionally installed based on the operating system or runtime environment?
From here
